From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6075 invoked by alias); 22 Sep 2009 15:35:02 -0000 Received: (qmail 6030 invoked by uid 22791); 22 Sep 2009 15:35:01 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mailhost.u-strasbg.fr (HELO mailhost.u-strasbg.fr) (130.79.200.156) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 Sep 2009 15:34:56 +0000 Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.14.2/jtpda-5.5pre1) with ESMTP id n8MFYn0r041333 ; Tue, 22 Sep 2009 17:34:49 +0200 (CEST) (envelope-from muller@ics.u-strasbg.fr) Received: from mailserver.u-strasbg.fr (ms2.u-strasbg.fr [IPv6:2001:660:2402:d::11]) by baal.u-strasbg.fr (8.14.0/jtpda-5.5pre1) with ESMTP id n8MFYnE6077223 ; Tue, 22 Sep 2009 17:34:49 +0200 (CEST) (envelope-from muller@ics.u-strasbg.fr) Received: from d620muller (www-ics.u-strasbg.fr [130.79.210.225]) (user=mullerp mech=LOGIN) by mailserver.u-strasbg.fr (8.14.3/jtpda-5.5pre1) with ESMTP id n8MFYm2I070992 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) ; Tue, 22 Sep 2009 17:34:48 +0200 (CEST) (envelope-from muller@ics.u-strasbg.fr) From: "Pierre Muller" To: "'Eli Zaretskii'" Cc: References: <002001ca3acf$a0d8bb40$e28a31c0$@u-strasbg.fr> <83hbuwurzc.fsf@gnu.org> In-Reply-To: <83hbuwurzc.fsf@gnu.org> Subject: RE: [RFA] windows-nat.c: Handle CTRL_BREAK_EVENT in ctrl_c_handler Date: Tue, 22 Sep 2009 15:35:00 -0000 Message-ID: <000601ca3b9a$3cbbe670$b633b350$@u-strasbg.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00704.txt.bz2 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=20 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=A0: gdb-patches-owner@sourceware.org [mailto:gdb-patches- > owner@sourceware.org] De la part de Eli Zaretskii > Envoy=E9=A0: Monday, September 21, 2009 7:29 PM > =C0=A0: Pierre Muller > Cc=A0: gdb-patches@sourceware.org > Objet=A0: Re: [RFA] windows-nat.c: Handle CTRL_BREAK_EVENT in > ctrl_c_handler >=20 > > From: "Pierre Muller" > > 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. >=20 > If this patch is accepted, please submit also a short change to the > manual, for the Windows-specific section, documenting this behavior. >=20 > Thanks.