Re: Ctrl-C strange behavior

[Scott A Sumner <sasumner@juno.com>]

Chris (& others)--

Actually it looked like there were three routines to hit:

1) gdbtk_start_timer
2) gdbtk_stop_timer
3) target_should_use_timer

I pulled the #ifdef conditionals out, and left the 'return's in.
Did I make the right call here?



>>My problem:  If my target runs at full speed, I have no way to tell
>>Insight I want to break execution wherever it happens to be.  As 
>>soon as
>>I hit the continue button, Insight changes the cursor to an 
>>hourglass and
>>just hangs (if I don't have a breakpoint set that execution will 
>>hit).  I
>>can't do anything except kill gdb and restart it.  I want to press 
>>the
>>stop button but as Insight appears to be hung at this point, it 
>>doesn't
>>work.  This is *extremely* annoying; anyone have any idea why it 
>>does
>>this and what the solution/workaround might be?
 
> Try removing the "#ifdef __CYGWIN32__" (sic) conditional in 
> gdbtk_start_timer
> and also try using the latest cygwin net release.  It's available 
> at:
> 
> http://sourceware.cygnus.com/cygwin/
> 
> cgf