Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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, 22 Sep 2009 15:35:00 -0000	[thread overview]
Message-ID: <000601ca3b9a$3cbbe670$b633b350$@u-strasbg.fr> (raw)
In-Reply-To: <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.


  reply	other threads:[~2009-09-22 15:35 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 [this message]
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
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='000601ca3b9a$3cbbe670$b633b350$@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