This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: cygheap problems, 20040326 snapshot
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 2 Apr 2004 20:50:33 -0500
- Subject: Re: cygheap problems, 20040326 snapshot
- References: <4064BA0C.8000108@fangorn.ca> <6.0.1.1.0.20040327003026.0285fd70@127.0.0.1> <40681F55.6050009@fangorn.ca> <Pine.GSO.4.58.0404021319020.21204@thing1-200> <406E1303.2060109@fangorn.ca>
- Reply-to: cygwin at cygwin dot 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/