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:51:26 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: What's a good stable snapshot DLL?
Message-ID: <20010416135126.C17910@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <8F23E55D511AD5119A6800D0B76FDDE11E0F0A AT cpex3 DOT channelpoint DOT com> <200104161740 DOT NAA13650 AT envy DOT delorie DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <200104161740.NAA13650@envy.delorie.com>; from dj@delorie.com on Mon, Apr 16, 2001 at 01:40:56PM -0400

On Mon, Apr 16, 2001 at 01:40:56PM -0400, DJ Delorie 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.

Yeah, I've been thinking about doing this.  Most of the debugging seems
like common sense, to me.  You set breakpoints and hope that they get
hit...

Or, you

set CYGWIN=error_start=x:\path\to\gdb.exe

and let cygwin pop up a copy of gdb when there is a SIGSEGV or something.

cgf

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