This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cygheap problems, 20040326 snapshot


Christopher Faylor wrote:
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.


I tried setting error_start as explained in winsup/cygwin/how-to-debug-cygwin.txt. However, gdb doesn't pop up when this error occurs. All I get is the same error message as before. I'm going to try Pierre's patch next.


Another data point: This error doesn't occur when I start cygpath, cygstart or gdb from the win2k cmd command prompt. It only occurs when I run these programs from bash or sh.


-- If it's not POSIX... it's CRAP!


-- 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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]