From: Eli Zaretskii <eliz@gnu.org>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] windows-nat.c: Handle CTRL_BREAK_EVENT in ctrl_c_handler
Date: Tue, 22 Sep 2009 17:58:00 -0000 [thread overview]
Message-ID: <83d45ivp5w.fsf@gnu.org> (raw)
In-Reply-To: <000601ca3b9a$3cbbe670$b633b350$@u-strasbg.fr>
> From: "Pierre Muller" <muller@ics.u-strasbg.fr>
> Cc: <gdb-patches@sourceware.org>
> Date: Tue, 22 Sep 2009 17:34:56 +0200
>
> I already checked the patch in,
Only the trunk or the branch as well?
> 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,
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. I hope GDB 7.0 will
not be released with the code but without the docs.
Thanks.
next prev parent reply other threads:[~2009-09-22 17:58 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 [this message]
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
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=83d45ivp5w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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