cygwin bughunt (FAQ alert?)

Joshua Daniel Franklin
Thu Jan 20 21:21:00 GMT 2005

> On Thu, Jan 20, 2005 at 08:12:31PM +0100, David Dindorp wrote:
> >Tracking it down with GDB to cygwin_split_path() : 0x61073e06 was easy.
On Thu, 20 Jan 2005 15:04:55 -0500, Christopher Faylor wrote:
> 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.

Sure, how about this:

I've found a bug in Cygwin, how can I debug it?

Debugging symbols are stripped from distibuted Cygwin binaries, so any
symbols that you
see in gdb are basically meaningless. It is also a good idea to use
the latest code in case the bug has been fixed, so you will need to
either build your own debugging version by following the instructions
at or use a current snapshot

Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list