Re: [RFC] win32-nat.c: Handle EXCEPTION_INVALID_HANDLE as SIGSYS

[Eli Zaretskii <eliz@gnu.org>]

> Date: Wed, 24 Oct 2007 15:37:35 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Pedro Alves <pedro_alves@portugalmail.pt>, muller@ics.u-strasbg.fr,
> 	gdb-patches@sourceware.org
> 
> > 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).
> 
> If whoever works on this is feeling ambitious, I would prefer a
> solution that is not too tightly linked to Windows.  I've worked with
> at least two different embedded developers this past year who were
> confused by the need to map platform-specific exceptions onto Unix
> signals.  An embedded PowerPC developer is likely to have a much
> better idea what's going on if we tell him that his code triggered
> a Machine Check Exception than if we report SIGBUS.

I agree.

(Actually, a careful reading of what I wrote would show that I never
suggested to do such a mapping, I just said that it isn't done by the
underlying library.)