From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21532 invoked by alias); 23 Apr 2010 20:27:27 -0000 Received: (qmail 21521 invoked by uid 22791); 23 Apr 2010 20:27:25 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from az33egw02.freescale.net (HELO az33egw02.freescale.net) (192.88.158.103) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 23 Apr 2010 20:27:22 +0000 Received: from az33smr01.freescale.net (az33smr01.freescale.net [10.64.34.199]) by az33egw02.freescale.net (8.14.3/az33egw02) with ESMTP id o3NKQxZa018312; Fri, 23 Apr 2010 13:26:59 -0700 (MST) Received: from cortelldt.freescale.com (cortelldt.am.freescale.net [10.82.136.164]) by az33smr01.freescale.net (8.13.1/8.13.0) with ESMTP id o3NKZA8B006004; Fri, 23 Apr 2010 15:35:13 -0500 (CDT) Message-Id: <201004232035.o3NKZA8B006004@az33smr01.freescale.net> Date: Fri, 23 Apr 2010 20:27:00 -0000 To: Joel Brobecker From: John Cortell Subject: Re: sending CTRL-C to Cygwin gdb 6.8 has no effect Cc: gdb@sourceware.org In-Reply-To: <20100423201109.GQ13204@adacore.com> References: <201004231941.o3NJfbWR021914@az33smr01.freescale.net> <20100423194404.GP13204@adacore.com> <201004232005.o3NK58Qu027711@az33smr01.freescale.net> <20100423201109.GQ13204@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-04/txt/msg00117.txt.bz2 At 03:11 PM 4/23/2010, Joel Brobecker wrote: >This is as much as I know without having to look deeper into this, >but that should give you enough info to figure out the rest... > >The change that improved the control-c behavior is the following one: > >| 2009-03-22 Nicolas Roche >| Christopher Faylor >| >| * win32-nat.c (ctrl_c_handler): New function. >| (win32_wait): Register ctrl_c_handler as Ctrl-C handler if >the inferior >| is run in a separate console. > > > Hm. That document tells me that gdb itself can interrupt a remote > > inferior, but how do I tell gdb to do so? I'm not a gdb expert, so > > perhaps this is a dumb question. > >It depends of your environement, but basically, you press ctrl-c, or >you get the IDE to send this ctrl-c to GDB. Ah, OK so I assume you're saying the ability to interrupt a remote inferrior is in HEAD and not 6.8. Since sending CTRL-C to cygwin gdb 6.8 is doing nothing for us when the inferior is local. I assume it would also do nothing for us if the inferior is remote. So, my point is that with cygwin gdb 6.8, CDT has to send the CTRL-C to the local inferior in order to interrupt the program, since sending it to gdb has no effect. I was looking for confirmation that it's a known issue (and not something wrong we're doing). But as I say that, it occurs to me...why isn't the issue reproducible at the cmdline? I.e., if the user hitting CTRL-C in a Windows shell gdb session successfully interrupts the target program, why is sending the CTRL-C programatically not working? Any thoughts there?