On Jan 20 17:00, Pierre A. Humblet wrote: > On Thu, Jan 20, 2005 at 12:47:33PM -0800, Joshua Daniel Franklin wrote: > > > > 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 http://cygwin.com/faq/faq_3.html#SEC102 or use a current snapshot > > from http://cygwin.com/snapshots/ > > This must be modulated by the warnings on the snapshot page, > so I would recommend an initial step: write to the list, describe > the bug and ask for a recommended snapshot. > Should we also provide an optional cygwin_debug package, with only > an unstripped cygwin1.dll.debug ?
I don't think so. I don't recall that any Linux distro contains a debug-enabled kernel. I guess, those who feel confident to debug the kernel (here: the Cygwin DLL), should be able to build their own debug version. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/
