This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: [RFA] windows-nat.c: Handle CTRL_BREAK_EVENT in ctrl_c_handler
- From: "Pierre Muller" <muller at ics dot u-strasbg dot fr>
- To: "'Eli Zaretskii'" <eliz at gnu dot org>
- Cc: <gdb-patches at sourceware dot org>
- Date: Tue, 22 Sep 2009 17:34:56 +0200
- Subject: RE: [RFA] windows-nat.c: Handle CTRL_BREAK_EVENT in ctrl_c_handler
- References: <002001ca3acf$a0d8bb40$e28a31c0$@u-strasbg.fr> <83hbuwurzc.fsf@gnu.org>
I already checked the patch in,
for the docs, here is what I wanted to add:
A running MS-Windows program can be interrupted by pressing @samp{Ctrl-C},
unless that program configured @samp{Ctrl-C} as a normal character by a call
to @code{SetConsoleMode}. In that case, @samp{Ctrl-Break} can still be used
to interrupt the running program.
I have no idea if I should add something like a @kindex...
But my main problem is that I don't know really where we should
put that inside the "Cygwin native" section.
I would suggest putting it right after the first paragraph,
but in fact it could also be with the general description of
running program interruption.
Please help me out,
Pierre Muller
Pascal language support maintainer for GDB
> -----Message d'origine-----
> De?: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé?: Monday, September 21, 2009 7:29 PM
> À?: Pierre Muller
> Cc?: gdb-patches@sourceware.org
> Objet?: Re: [RFA] windows-nat.c: Handle CTRL_BREAK_EVENT in
> ctrl_c_handler
>
> > From: "Pierre Muller" <muller@ics.u-strasbg.fr>
> > Date: Mon, 21 Sep 2009 17:24:35 +0200
> >
> > This patch allows me to interrupt a debuggee
> > running in another console (with 'set new-console on')
> > by pressing Ctrl-Break, even, if Ctrl-C has been
> > transformed by the debuggee as a normal char
> > using SetConsoleMode API function.
>
> If this patch is accepted, please submit also a short change to the
> manual, for the Windows-specific section, documenting this behavior.
>
> Thanks.