From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Faylor <cgf@cygnus.com>
To: Scott A Sumner <sasumner@juno.com>
Cc: insight@sourceware.cygnus.com, jmills@tga.com, bgat@open-widgets.com
Subject: Re: Ctrl-C strange behavior
Date: Wed, 03 May 2000 17:45:00 -0000
Message-id: <20000503204515.A11025@cygnus.com>
References: <20000503.195747.-291705.0.sasumner@juno.com>
X-SW-Source: 2000-q2/msg00173.html

On Wed, May 03, 2000 at 07:23:59PM -0400, Scott A Sumner wrote:
>Hi Leon and everyone,
>
>I've noticed some strange behavior with Insight similar to Leon's.  BTW,
>my Insight is configured as "--host=i586-pc-cygwin --target=m68k-coff"
>and is the 20000314 snapshot.
>
>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