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 [thread overview]
Message-ID: <20000503204515.A11025@cygnus.com> (raw)
In-Reply-To: <20000503.195747.-291705.0.sasumner@juno.com>
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
next prev parent reply other threads:[~2000-05-03 17:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 17:00 Scott A Sumner
2000-05-03 17:45 ` Chris Faylor [this message]
2000-05-04 8:58 ` Keith Seitz
-- strict thread matches above, loose matches on Subject: below --
2000-05-22 9:14 Will Lentz
2000-05-22 9:18 ` Elena Zannoni
2000-05-16 11:08 Will Lentz
2000-05-22 7:58 ` Elena Zannoni
2000-05-05 13:30 Scott A Sumner
2000-05-12 11:11 ` Elena Zannoni
2000-05-02 10:32 Leon Pollak
2000-05-04 9:10 ` Keith Seitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000503204515.A11025@cygnus.com \
--to=cgf@cygnus.com \
--cc=bgat@open-widgets.com \
--cc=insight@sourceware.cygnus.com \
--cc=jmills@tga.com \
--cc=sasumner@juno.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).