cygwin bughunt (FAQ alert?)

Christopher Faylor
Thu Jan 20 20:47:00 GMT 2005

On Thu, Jan 20, 2005 at 08:12:31PM +0100, David Dindorp wrote:
>Larry Hall wrote:
>> I have the following suggestions/questions:
>>  1. Did you try a Cygwin 1.5.12 or even a snapshot?
>No.  I'm using 1.5.10, and it still smells *real* fresh, I think ;-).
>Also, the problem only occurs on a customer system which unfortunately
>I can't go around and upgrade all the time "just to see".
>I don't have regular access to it either.
>>  2. Is this a local debug build of Cygwin or stock 1.5.10.  If the 
>>     latter, you might find building a debug version is more help.
>Stock 1.5.10.
>There's a debug version?  These are the things I need to know!
>Found the "how-to-debug-cygwin" document buried deep in some bz2 file,
>I'll go read that now.
>In the above statement, you sort-of imply that building a debug version
>is wrong if using a stock version..  I should do what then?
>> If there is a race issue here, you're going to need to work with the 
>> code to find it.
>That's what I'm basically trying to do.
>Tracking it down with GDB to cygwin_split_path() : 0x61073e06 was easy.

Since cygwin isn't built with debugging symbols, the symbols that you do
see in gdb are basically meaningless.

I think this has come up often enough to be a FAQ.  Joshua?

In any event, you do need to either build a debugging version or, possibly,
use a snapshot from since those are currently
built with debugging turned on.


Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list