From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eliz@gnu.org
Cc: pedro_alves@portugalmail.pt, muller@ics.u-strasbg.fr,
gdb-patches@sourceware.org
Subject: Re: [RFC] win32-nat.c: Handle EXCEPTION_INVALID_HANDLE as SIGSYS
Date: Wed, 24 Oct 2007 19:37:00 -0000 [thread overview]
Message-ID: <200710241929.l9OJTGcQ021035@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <ur6jktjbs.fsf@gnu.org> (message from Eli Zaretskii on Wed, 24 Oct 2007 21:15:51 +0200)
> Date: Wed, 24 Oct 2007 21:15:51 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > Date: Wed, 24 Oct 2007 09:39:58 +0100
> > From: "Pedro Alves" <pedro_alves@portugalmail.pt>
> > Cc: gdb-patches@sourceware.org
> >
> > Maybe we can take the oportunity to implement more generic Windows exceptions
> > support, not just EXCEPTION_INVALID_HANDLE.
>
> I think it's a good idea. In my experience, any serious program that
> wants to handle signals and exceptions on Windows cannot avoid
> supporting a large number of important EXCEPTION_* exceptions, because
> unlike on Posix platforms, most of them are not translated into SIG*
> style signals, at least in native Windows programs (as opposed to
> Cygwin).
People might want to look at how we handle Mach exceptions; see
signal/signal.c and gnu-nat.c.
next prev parent reply other threads:[~2007-10-24 19:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 14:14 Pierre Muller
2007-10-22 21:15 ` Eli Zaretskii
2007-10-23 22:06 ` Christopher Faylor
2007-10-23 22:26 ` Daniel Jacobowitz
2007-10-24 5:21 ` Eli Zaretskii
2007-10-24 8:40 ` Pierre Muller
2007-10-24 19:07 ` Eli Zaretskii
2007-10-24 11:47 ` Pedro Alves
2007-10-24 8:13 ` Pierre Muller
2007-10-24 8:51 ` Pedro Alves
2007-10-24 19:19 ` Eli Zaretskii
2007-10-24 19:37 ` Mark Kettenis [this message]
2007-10-24 19:40 ` Daniel Jacobowitz
2007-10-24 20:15 ` Eli Zaretskii
2007-10-29 8:25 ` Christopher Faylor
2007-10-29 3:07 ` Christopher Faylor
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=200710241929.l9OJTGcQ021035@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=pedro_alves@portugalmail.pt \
/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