From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23424 invoked by alias); 24 Oct 2007 08:13:41 -0000 Received: (qmail 23416 invoked by uid 22791); 24 Oct 2007 08:13:40 -0000 X-Spam-Check-By: sourceware.org Received: from ics.u-strasbg.fr (HELO ics.u-strasbg.fr) (130.79.112.250) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 24 Oct 2007 08:13:37 +0000 Received: from ICSMULLER (laocoon.u-strasbg.fr [130.79.112.72]) by ics.u-strasbg.fr (Postfix) with ESMTP id 3987E18701E; Wed, 24 Oct 2007 10:18:04 +0200 (CEST) From: "Pierre Muller" To: "'Eli Zaretskii'" , References: <008101c814b1$9aeb2dd0$d0c18970$@u-strasbg.fr> <20071023214730.GB5570@ednor.casa.cgf.cx> In-Reply-To: Subject: RE: [RFC] win32-nat.c: Handle EXCEPTION_INVALID_HANDLE as SIGSYS Date: Wed, 24 Oct 2007 08:40:00 -0000 Message-ID: <001a01c81615$c58a7950$509f6bf0$@u-strasbg.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-10/txt/msg00567.txt.bz2 > -----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 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