Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 2 Apr 2004 20:50:33 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygheap problems, 20040326 snapshot Message-ID: <20040403015033.GA25870@coc.bosbc.com> Mail-Followup-To: cygwin@cygwin.com References: <4064BA0C.8000108@fangorn.ca> <6.0.1.1.0.20040327003026.0285fd70@127.0.0.1> <40681F55.6050009@fangorn.ca> <406E1303.2060109@fangorn.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <406E1303.2060109@fangorn.ca> User-Agent: Mutt/1.4.1i Reply-To: cygwin@cygwin.com On Fri, Apr 02, 2004 at 08:27:32PM -0500, Mark Blackburn wrote: >Brian Ford wrote: >>On Mon, 29 Mar 2004, Mark Blackburn wrote: >>>No it isn't. I recently tried my own build of cygwin: >>> >>Could you possibly build it with the attached patch and report the >>strace output? Also, if you could scan >>cygwin/winsup/cygwin/how-to-debug-cygwin.txt, it will tell you how to >>get a working gdb to debug this. The output of info dll would be >>interesting. Thanks. > >Unfortunately the failure doesn't occur when things (gdb & cygstart) >are run under strace. Here's the output when run normally: Use the "error_start" option to the CYGWIN environment variable. It will cause gdb to pop up when the error occurs. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/