From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFA] windows-nat.c: Handle CTRL_BREAK_EVENT in ctrl_c_handler
Date: Tue, 29 Sep 2009 07:29:00 -0000 [thread overview]
Message-ID: <000001ca40d6$9ac3c260$d04b4720$@u-strasbg.fr> (raw)
In-Reply-To: <83ocoxsl83.fsf@gnu.org>
Could we apply both
the patch to windows-nat.c and to docs to branch
or is it too late?
Pierre
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé : Saturday, September 26, 2009 6:51 PM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFA] windows-nat.c: Handle CTRL_BREAK_EVENT in
> ctrl_c_handler
>
> > Date: Tue, 22 Sep 2009 20:56:43 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> > Cc: gdb-patches@sourceware.org
> >
> > Your text is mostly okay, but it needs to use a different markup for
> > the Ctrl-C etc.
> >
> > I will fix it and install it in a couple of days.
>
> Done. Here's what I committed:
>
> 2009-09-26 Pierre Muller <muller@ics.u-strasbg.fr>
>
> * gdb.texinfo (Cygwin Native): Mention support for Ctrl-BREAK.
>
> Index: gdb.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
> retrieving revision 1.628
> diff -u -r1.628 gdb.texinfo
> --- gdb.texinfo 21 Sep 2009 12:48:36 -0000 1.628
> +++ gdb.texinfo 26 Sep 2009 16:45:54 -0000
> @@ -15900,10 +15900,20 @@
> @cindex Cygwin-specific commands
>
> @value{GDBN} supports native debugging of MS Windows programs,
> including
> -DLLs with and without symbolic debugging information. There are
> various
> -additional Cygwin-specific commands, described in this section.
> -Working with DLLs that have no debugging symbols is described in
> -@ref{Non-debug DLL Symbols}.
> +DLLs with and without symbolic debugging information.
> +
> +@cindex Ctrl-BREAK, MS-Windows
> +@cindex interrupt debuggee on MS-Windows
> +MS-Windows programs that call @code{SetConsoleMode} to switch off the
> +special meaning of the @samp{Ctrl-C} keystroke cannot be interrupted
> +by typing @kbd{C-c}. For this reason, @value{GDBN} on MS-Windows
> +supports @kbd{C-@key{BREAK}} as an alternative interrupt key
> +sequence, which can be used to interrupt the debuggee even if it
> +ignores @kbd{C-c}.
> +
> +There are various additional Cygwin-specific commands, described in
> +this section. Working with DLLs that have no debugging symbols is
> +described in @ref{Non-debug DLL Symbols}.
>
> @table @code
> @kindex info w32
next prev parent reply other threads:[~2009-09-29 7:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 15:24 Pierre Muller
2009-09-21 17:31 ` Eli Zaretskii
2009-09-22 15:35 ` Pierre Muller
2009-09-22 17:58 ` Eli Zaretskii
2009-09-22 18:05 ` Joel Brobecker
2009-09-22 22:02 ` Pierre Muller
2009-09-26 16:49 ` Eli Zaretskii
2009-09-29 7:29 ` Pierre Muller [this message]
2009-09-29 14:15 ` Joel Brobecker
2009-09-29 14:33 ` Pierre Muller
2009-09-30 20:09 ` Christopher Faylor
2009-09-30 20:13 ` Christopher Faylor
2009-09-29 18:55 ` Eli Zaretskii
2009-09-29 21:22 ` Joel Brobecker
2009-09-30 7:42 ` Pierre Muller
2009-09-21 17:37 ` Daniel Jacobowitz
2009-09-21 22:15 ` Christopher Faylor
2009-09-21 22:39 ` Pierre Muller
2009-09-22 15:49 ` Joel Brobecker
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='000001ca40d6$9ac3c260$d04b4720$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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