This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Debugging the cygwin DLL
- To: curtis@pdi.com
- Subject: Re: Debugging the cygwin DLL
- From: DJ Delorie <dj@delorie.com>
- Date: Mon, 22 Feb 1999 18:35:52 -0500
- CC: cygwin@sourceware.cygnus.com
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- In-reply-to: <36D1E0A5.D4B841D2@pdi.com> (message from Curtis Galloway on Mon,22 Feb 1999 14:56:37 -0800)
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- References: <36D1D392.2FA663A3@pdi.com> <199902222212.RAA01050@envy.delorie.com> <36D1E0A5.D4B841D2@pdi.com>
- Sender: cygwin-owner@sourceware.cygnus.com
> 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.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com