From: "Pedro Alves" <pedro_alves@portugalmail.pt>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] win32-nat.c: Handle EXCEPTION_INVALID_HANDLE as SIGSYS
Date: Wed, 24 Oct 2007 11:47:00 -0000 [thread overview]
Message-ID: <4053daab0710240151m322d1fc6yc2efa6a6b5058e1e@mail.gmail.com> (raw)
In-Reply-To: <ubqaprw81.fsf@gnu.org>
Eli Zaretskii wrote:
> > Date: Tue, 23 Oct 2007 17:47:30 -0400
> > From: Christopher Faylor
> >
> > 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.
>
I'll do my best to help review MinGW patches. Often I'll need a bit more
time to get to it, and often will only be able to in weekends. But, I'll get to
them.
> Which is exactly the reason I suggested to make MinGW a separate
> target with a separate *-nat.c file.
>
Not just yet please :) I'm sure that when the patches will be split, they'll be
rather smallish. Hey, it was an RFC, not an RFA!
Cheers,
Pedro Alves
next prev parent reply other threads:[~2007-10-24 8:51 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 [this message]
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=4053daab0710240151m322d1fc6yc2efa6a6b5058e1e@mail.gmail.com \
--to=pedro_alves@portugalmail.pt \
--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