From: DJ Delorie <dj@delorie.com>
To: curtis@pdi.com
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Debugging the cygwin DLL
Date: Mon, 22 Feb 1999 15:36:00 -0000 [thread overview]
Message-ID: <199902222335.SAA01566@envy.delorie.com> (raw)
In-Reply-To: < 36D1E0A5.D4B841D2@pdi.com > (message from Curtis Galloway on Mon,22 Feb 1999 14:56:37 -0800)
> 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
WARNING: multiple messages have this Message-ID
From: DJ Delorie <dj@delorie.com>
To: curtis@pdi.com
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Debugging the cygwin DLL
Date: Sun, 28 Feb 1999 23:02:00 -0000 [thread overview]
Message-ID: <199902222335.SAA01566@envy.delorie.com> (raw)
Message-ID: <19990228230200.00Eh9YIb7xBZzndLg4-UTqKKsDGG-fAz4pzdYzAOeK0@z> (raw)
In-Reply-To: <36D1E0A5.D4B841D2@pdi.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
next prev parent reply other threads:[~1999-02-22 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-22 14:02 Curtis Galloway
[not found] ` < 36D1D392.2FA663A3@pdi.com >
1999-02-22 14:12 ` DJ Delorie
1999-02-22 15:06 ` Curtis Galloway
[not found] ` < 36D1E0A5.D4B841D2@pdi.com >
1999-02-22 15:36 ` DJ Delorie [this message]
1999-02-28 23:02 ` Christopher Faylor
1999-02-28 23:02 ` DJ Delorie
1999-02-28 23:02 ` Curtis Galloway
1999-02-28 23:02 ` DJ Delorie
1999-02-28 23:02 ` Curtis Galloway
1999-02-22 14:33 Earnie Boyd
1999-02-28 23:02 ` Earnie Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199902222335.SAA01566@envy.delorie.com \
--to=dj@delorie.com \
--cc=curtis@pdi.com \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).