Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Hannu E K Nevalainen \(garbage mail\)" To: Subject: RE: cygwin1.dll - debug version (RE: similar crash in mmap for 1.5.3-1) Date: Wed, 10 Sep 2003 22:27:10 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <20030910160007.GC29506@redhat.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Hannu: > >>>Most likely... Some wording regarding "download the debug info" needs > >>>to be added to "problems.html" - I guess. > >> CGF: > >>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"... Indeed... with some more words that points to useful information... or? > >>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. :-) ...have I heard those words before? Have I spoken in the same manner myself? ;-) > >FWIW, I think Hannu has a point in that if debugging information were > >available, it would be much easier for people to step in and outline > >the necessary actions to provide a good stack trace than it would be to > >show them how to build a debug version of the DLL from scratch. Just > >my 2c. > > "This is not a bad idea...it just requires some time which I don't have > right now." > > I haven't, so far, seen anyone chime in usefully on this issue when > people have provided stack traces. There are other issues which would > crop up even if debugging info were available like the fact that traces > are unreliable where they include functions without stack frame info. > > 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. /Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E -- [1] I've been investigating AmigaOS executables _thoroughly_ and thus know that some stuff do require intimate knowledge of OS internals. --END OF MESSAGE-- -- 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/