From: Eli Zaretskii <eliz@gnu.org>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org, pedro_alves@portugalmail.pt, drow@false.org
Subject: Re: [RFC] win32-nat.c: Handle EXCEPTION_INVALID_HANDLE as SIGSYS
Date: Mon, 22 Oct 2007 21:15:00 -0000 [thread overview]
Message-ID: <uwstesw73.fsf@gnu.org> (raw)
In-Reply-To: <008101c814b1$9aeb2dd0$d0c18970$@u-strasbg.fr> (muller@ics.u-strasbg.fr)
> From: "Pierre Muller" <muller@ics.u-strasbg.fr>
> Cc: "'Pedro Alves'" <pedro_alves@portugalmail.pt>, "'Daniel Jacobowitz'" <drow@false.org>
> Date: Mon, 22 Oct 2007 15:44:01 +0200
>
> The patch first implements recognition of
> the exception EXCEPTION_INVALID_HANDLE generated
> by a call to CloseHandle with an invalid parameter.
Thanks.
> The new variable stop_on_invalid_handle,
> which can be set via "set stoponinvalidhandle",
> allows to either ignore that exception completely
> (with just a comment if verbose is set, default behavior),
> or to map it to SIGSYS, which can then be handled as any
> target signal via "handle SIGSYS ..."
I don't know if Chris (and others) will approve this change, but if
they do, please submit a suitable change for the manual describing
this setting, before committing the code changes. I don't want us to
have commands that are not documented in the manual.
Thanks again for working on this.
next prev parent reply other threads:[~2007-10-22 21:09 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 [this message]
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
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=uwstesw73.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=pedro_alves@portugalmail.pt \
/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