This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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



> -----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




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]