On Wed, Sep 10, 2003 at 10:27:10PM +0200, Hannu E K Nevalainen (garbage mail) wrote: >> Also, the problems.html page is surely the wrong place for a tutorial >> for how to debug the cygwin DLL. A hyperlink to a page which talked >> about this, with a caveat about this being only for the technically >> savvy, would be fine. But I'm not going to write it. Volunteers? > > Well, there needn't be a _tutorial_ on debugging. Maybe just a link to a >good starting point for understanding gdb/ddd/insight and their usage - for >beginners [1]. > Non-beginners often need just a few words... these words should be added >though - time permitting, as always.
I think you are missing my point. I do not want a problems page to be littered with a "and here's how you debug cygwin" or here's where to find debuggers. That would be daunting to people who are already daunted by the amount of info on that page. A hyperlink with something like: - Consider <a href="debugcygwin.html">debugging cygwin</a> yourself or possibly <a href="debugcygwin.html#backtrace">providing a back trace</a> of a failing application. I have a fundamental problem with adding tutorials on debugging here. Go to the gdb page if you want to learn how to debug something. A (very) few pointers on how to debug with a DLL are fine, since they would be cygwin-specific. But info on setting breakpoints, etc., really should come from the experts. I'm also *extremely* dubious that we'd get useful information from someone who has never heard of a debugger or even someone who hasn't heard about gdb. Anyway, as usual, we're discussing something that will probably never happen. I'm finished now since I've already used up too much time reiterating points. My next act will be to review any documentation provided. -- 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/
