From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>, <gdb-patches@sourceware.org>
Subject: RE: [RFC] win32-nat.c: Handle EXCEPTION_INVALID_HANDLE as SIGSYS
Date: Wed, 24 Oct 2007 08:40:00 -0000 [thread overview]
Message-ID: <001a01c81615$c58a7950$509f6bf0$@u-strasbg.fr> (raw)
In-Reply-To: <ubqaprw81.fsf@gnu.org>
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Eli Zaretskii
> Sent: Wednesday, October 24, 2007 6:08 AM
> To: gdb-patches@sourceware.org
> Subject: Re: [RFC] win32-nat.c: Handle EXCEPTION_INVALID_HANDLE as
> SIGSYS
>
> > Date: Tue, 23 Oct 2007 17:47:30 -0400
> > From: Christopher Faylor <cgf-use-the-mailinglist-
> please@sourceware.org>
> >
> > And, amusingly enough, this patch illustrates, within days of making
> > mingw available, exactly the kind of situation I didn't want to get
> into
> > by allowing gdb to build under MinGW. It forces me to evaluate a
> > multipage patch which isn't needed for Cygwin.
>
> Which is exactly the reason I suggested to make MinGW a separate
> target with a separate *-nat.c file.
Why?
- All the changes I propose should apply to both cygwin and mingw
ports.
The only reason why there is a behavior difference between the cygwin
compiled gdb and the mingw compiled one is that
in the cygwin exception handler,
EXCEPTION_INVALID_HANDLE is ignored, while mingw exception handler
does not handle it, and thus the problem shows up only
when debugging the mingw compiled gdb executable.
Pierre
next prev parent reply other threads:[~2007-10-24 8:13 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 [this message]
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
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='001a01c81615$c58a7950$509f6bf0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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