From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10594 invoked by alias); 22 Sep 2009 17:58:54 -0000 Received: (qmail 10586 invoked by uid 22791); 22 Sep 2009 17:58:53 -0000 X-SWARE-Spam-Status: No, hits=-0.3 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout3.012.net.il (HELO mtaout3.012.net.il) (84.95.2.7) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 Sep 2009 17:58:47 +0000 Received: from conversion-daemon.i_mtaout3.012.net.il by i_mtaout3.012.net.il (HyperSendmail v2004.12) id <0KQD00C00WF0M400@i_mtaout3.012.net.il> for gdb-patches@sourceware.org; Tue, 22 Sep 2009 20:58:44 +0300 (IDT) Received: from HOME-C4E4A596F7 ([77.124.4.167]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KQD00L5CWLVJ020@i_mtaout3.012.net.il>; Tue, 22 Sep 2009 20:58:44 +0300 (IDT) Date: Tue, 22 Sep 2009 17:58:00 -0000 From: Eli Zaretskii Subject: Re: [RFA] windows-nat.c: Handle CTRL_BREAK_EVENT in ctrl_c_handler In-reply-to: <000601ca3b9a$3cbbe670$b633b350$@u-strasbg.fr> To: Pierre Muller Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83d45ivp5w.fsf@gnu.org> References: <002001ca3acf$a0d8bb40$e28a31c0$@u-strasbg.fr> <83hbuwurzc.fsf@gnu.org> <000601ca3b9a$3cbbe670$b633b350$@u-strasbg.fr> X-IsSubscribed: yes 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/msg00707.txt.bz2 > From: "Pierre Muller" > Cc: > 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.