From: Christopher Faylor <cgf@redhat.com>
To: gdb-patches@sources.redhat.com
Cc: jeremy@deadbeef.com
Subject: Re: gdb patch take 6
Date: Fri, 14 Nov 2003 19:22:00 -0000 [thread overview]
Message-ID: <20031114192159.GA23163@redhat.com> (raw)
In-Reply-To: <06f801c386a0$200cb960$966fa8c0@hksys.com>
[no personal replies please, reply-to set -- beware!]
On Mon, Sep 29, 2003 at 10:41:05AM -0500, Jeremy Bettis wrote:
>* gdb/win32-nat.c
>(handle_exception,get_child_debug_event,_initialize_inftarg) When debugging
>a program that uses windows SEH gdb stops the program even if the inferior's
>exception handler catches the exception. I have added a new set option,
>"set mapexceptionstosignals off" that will cause gdb to completely ignore
>WIN32 exceptions. This is similar to the feature "set signal-exceptions 4"
>in the Apple Openstep version of gdb 4.15.3.
I've been keeping this in my inbox for a while but, on checking with the
FSF assignment coordinator, it looks like there still isn't a gdb assignment
on file.
So, please resubmit if/when an assignment clears.
Thanks,
cgf
next prev parent reply other threads:[~2003-11-14 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 15:40 Jeremy Bettis
2003-11-14 19:22 ` Christopher Faylor [this message]
2003-11-14 21:19 ` Jeremy Bettis
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=20031114192159.GA23163@redhat.com \
--to=cgf@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jeremy@deadbeef.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