Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	Christopher Faylor <cgf AT cygnus DOT com>
Date:	Tue, 23 Feb 1999 21:52:23 -0500
To:	DJ Delorie <dj AT delorie DOT com>
Cc:	curtis AT pdi DOT com, cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: Debugging the cygwin DLL
Message-ID:	<19990223215223.B23525@cygnus.com>
References:	<36D1D392 DOT 2FA663A3 AT pdi DOT com> <199902222212 DOT RAA01050 AT envy DOT delorie DOT com> <36D1E0A5 DOT D4B841D2 AT pdi DOT com> <199902222335 DOT SAA01566 AT envy DOT delorie DOT com>
Mime-Version:	1.0
X-Mailer:	Mutt 0.95.1i
In-Reply-To:	<199902222335.SAA01566@envy.delorie.com>; from DJ Delorie on Mon, Feb 22, 1999 at 06:35:52PM -0500

On Mon, Feb 22, 1999 at 06:35:52PM -0500, DJ Delorie wrote:
>
>> Unfortunately, gdb's use of signals seems to interfere with
>> debugging the cygwin signal handling code.  I think I'm stuck with
>> using strace after all.
>
>Signals are just barely supported in gdb as is.  Chris and I also use
>strace to debug them.

Cygwin signals should be handled better in one of the recent gdb snapshots
if any adventurous soul would like to try to compile a new cygwin gdb.

The new snapshot should also allow some thread support as well as the
ability to attach to a running process using the *Win32* pid (not the
cygwin pid).

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -