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
Date:	Mon, 16 Apr 2001 13:40:56 -0400
Message-Id:	<200104161740.NAA13650@envy.delorie.com>
X-Authentication-Warning:	envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From:	DJ Delorie <dj AT delorie DOT com>
To:	troy DOT noble AT channelpoint DOT com
CC:	lhall AT rfk DOT com, cygwin AT cygwin DOT com
In-reply-to:	<8F23E55D511AD5119A6800D0B76FDDE11E0F0A@cpex3.channelpoint.com>
	(message from Troy Noble on Mon, 16 Apr 2001 11:35:01 -0600)
Subject:	Re: What's a good stable snapshot DLL?
References:	<8F23E55D511AD5119A6800D0B76FDDE11E0F0A AT cpex3 DOT channelpoint DOT com>

> 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.

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

- Raw text -