Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	"Bobby McNulty" <bobbymcn AT bellsouth DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: What's a good stable snapshot DLL?
Date:	Mon, 16 Apr 2001 15:52:16 -0000
Message-ID:	<CIEJIJIGGOKLEHGENHFJCEBOCAAA.bobbymcn@bellsouth.net>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to:	<20010416143619.A18970@redhat.com>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200
Importance:	Normal

Christopher, I am starting a regime of debugging all of the cygwin
distributiion.
It will take me a few weeks to fully implement. Stage 1 is happening right
now.
I, with much consideration, am downloading the source code and am going to
compile each one with
debugging information without -O2, as, from what I heard, that messes up the
debugging phase.

-----Original Message-----
From: cygwin-owner AT sources DOT redhat DOT com
[mailto:cygwin-owner AT sources DOT redhat DOT com]On Behalf Of Christopher Faylor
Sent: Monday, April 16, 2001 6:36 PM
To: Christopher Faylor
Subject: Re: What's a good stable snapshot DLL?


On Mon, Apr 16, 2001 at 10:20:44PM +0400, egor duda wrote:
>Hi!
>
>Monday, 16 April, 2001 Christopher Faylor cgf AT redhat DOT com wrote:
>
>>>> This is probably a FAQ.  Are the cygwin1.dll snapshots generated
>>>> with debug symbols such that I'll get more information in my Dr Watson
>>>> reports?  If not, do I need to build my own with VC++ 6.0 such that I
>>>> can pull up the debugger when (if) I get the access violations?
>>>
>>>Snapshots are built with gcc, not vc, so even if there's debug
>>>information in it, DrWatson won't see it.
>>>
>>>If you're going to be debugging the dll, you should get the sources
>>>from CVS and built it yourself, and use gdb to debug.  That will give
>>>you the best environment.  However, you'll need to build a copy of gdb
>>>that uses a "debug" version of cygwin, so as to avoid using the dll
>>>you're debugging.  Chris - perhaps you should create a web page on how
>>>you debug the dll?  You've had the most experience with this.
>
>CF> Yeah, I've been thinking about doing this.  Most of the debugging seems
>CF> like common sense, to me.  You set breakpoints and hope that they get
>CF> hit...
>
>i think almost everything starts to seem like common sense after you
>spent several days debugging some non-trivial bug in cygwin1.dll :-)
>At least, from my experience.

I'm not saying that there aren't special tricks that you learn as
you are debugging gdb.

However, most people can't seem to make it to step one -- run gdb.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -