On Wed, Sep 10, 2003 at 01:23:56PM +0200, Hannu E K Nevalainen (garbage mail) wrote: >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf >> Of Christopher Faylor > ><SNIP> >> >Idea, to help debug things like the above: >> > >> > Alt 1) Make an _unstripped_ cygwin1.dll available in a package named >> > "cygwin-DEBUG-dll" or some such. Also make it be >> "TEST/Exp" forever. >> > Alt 2) Have an unstripped cygwin1-DEBUG.dll added to the basic package, >> > add a simple "cygswapdll" utility. >> > >> >Is this a Good or Bad idea? >> >> The new version of binutils allows you to strip debug information and put >> it in a separate file. Then you can provide that file to gdb and use it >> for debugging. > > Right, now that you mention it I remember seeing it. My ideas ran obsolete >already in the start ':-> . > >> However, like everything there are two problems 1) lack of tuit cycles and >> 2) it won't stop people from running gdb on their binaries and reporting >> that strdup is causing a problem in mmap. There will still be a "download >> the debug info" step no matter what. > > Most likely... Some wording regarding "download the debug info" needs to be >added to "problems.html" - I guess.
That sort of presupposes that someone is interested in walking people through the debugging of the cygwin DLL. I know I'm not interested and I haven't seen anyone else step in when people start asking debugging questions. I guess the words in problems.html could be extended with a "You're basically on your own"... This is not a bad idea, especially since I thought of it myself long ago :-), like I said, it just requires some time which I don't have right now. 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/
