From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13032 invoked by alias); 23 Apr 2010 19:57:27 -0000 Received: (qmail 13023 invoked by uid 22791); 23 Apr 2010 19:57:26 -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 19:57:20 +0000 Received: from az33smr01.freescale.net (az33smr01.freescale.net [10.64.34.199]) by az33egw02.freescale.net (8.14.3/az33egw02) with ESMTP id o3NJutm6009493; Fri, 23 Apr 2010 12:56:55 -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 o3NK58Qu027711; Fri, 23 Apr 2010 15:05:08 -0500 (CDT) Message-Id: <201004232005.o3NK58Qu027711@az33smr01.freescale.net> Date: Fri, 23 Apr 2010 19:57: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: <20100423194404.GP13204@adacore.com> References: <201004231941.o3NJfbWR021914@az33smr01.freescale.net> <20100423194404.GP13204@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/msg00115.txt.bz2 At 02:44 PM 4/23/2010, Joel Brobecker wrote: > > In CDT, we've had to resort to sending a CTRL-C to the inferior > > process of a Cygwin gdb session because gdb itself doesn't react to > > the CTRL-C. Is this a known issue? Is it addressed in HEAD? > >This should have been fixed in recent versions of GDB. I don't remember >which version first started having the fix, but it's a safe bet that 7.1 >will. It for sure isn't present in MinGW 7.0 gdb, but then again, the problem is also not in their 6.8 version (not that it works well, btw, but it does interrupt it). As Cygwin gdb 7.0 isn't available other than in source form (and I don't have the cycles or motivation to build it from source), I figured I'd ask the list. > > Naturally, that approach isn't an option when debugging a remote > > program. > >But when you are doing remote debugging, the transport protocol used >between GDB and the target should provide a way to send that interrupt. >For instance, when using the remote protocol: > > >http://www.sourceware.org/gdb/current/onlinedocs/gdb/Interrupts.html#Interrupts 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.