From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9247 invoked by alias); 24 Oct 2007 19:37:13 -0000 Received: (qmail 9236 invoked by uid 22791); 24 Oct 2007 19:37:13 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO brahms.sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 24 Oct 2007 19:37:09 +0000 Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by brahms.sibelius.xs4all.nl (8.14.1/8.14.0) with ESMTP id l9OJTHqI016195; Wed, 24 Oct 2007 21:29:17 +0200 (CEST) Received: (from kettenis@localhost) by brahms.sibelius.xs4all.nl (8.14.1/8.14.1/Submit) id l9OJTGcQ021035; Wed, 24 Oct 2007 21:29:16 +0200 (CEST) Date: Wed, 24 Oct 2007 19:37:00 -0000 Message-Id: <200710241929.l9OJTGcQ021035@brahms.sibelius.xs4all.nl> From: Mark Kettenis To: eliz@gnu.org CC: pedro_alves@portugalmail.pt, muller@ics.u-strasbg.fr, gdb-patches@sourceware.org In-reply-to: (message from Eli Zaretskii on Wed, 24 Oct 2007 21:15:51 +0200) Subject: Re: [RFC] win32-nat.c: Handle EXCEPTION_INVALID_HANDLE as SIGSYS References: <008101c814b1$9aeb2dd0$d0c18970$@u-strasbg.fr> <20071023214730.GB5570@ednor.casa.cgf.cx> <001301c81613$d5492730$7fdb7590$@u-strasbg.fr> <4053daab0710240139o1898369jc54fbb75c6c48cef@mail.gmail.com> 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/msg00612.txt.bz2 > Date: Wed, 24 Oct 2007 21:15:51 +0200 > From: Eli Zaretskii > > > Date: Wed, 24 Oct 2007 09:39:58 +0100 > > From: "Pedro Alves" > > Cc: gdb-patches@sourceware.org > > > > Maybe we can take the oportunity to implement more generic Windows exceptions > > support, not just EXCEPTION_INVALID_HANDLE. > > 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). People might want to look at how we handle Mach exceptions; see signal/signal.c and gnu-nat.c.