Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Christopher Faylor Date: Tue, 23 Feb 1999 21:52:23 -0500 To: DJ Delorie Cc: curtis@pdi.com, cygwin@sourceware.cygnus.com Subject: Re: Debugging the cygwin DLL Message-ID: <19990223215223.B23525@cygnus.com> References: <36D1D392.2FA663A3@pdi.com> <199902222212.RAA01050@envy.delorie.com> <36D1E0A5.D4B841D2@pdi.com> <199902222335.SAA01566@envy.delorie.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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@sourceware.cygnus.com