Re: sending CTRL-C to Cygwin gdb 6.8 has no effect

[John Cortell <rat042@freescale.com>]

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.