From: Grant Edwards <grante@visi.com>
To: gdb@sources.redhat.com
Subject: RDI code busy-waiting on running target?
Date: Thu, 11 Jul 2002 15:55:00 -0000 [thread overview]
Message-ID: <20020711175854.A29971@visi.com> (raw)
[gdb 5.1.1, rdi target]
I've noticed that gdb uses all the CPU it can get while the
target is running (e.g. busy-waiting 'till target stops).
I'm building 5.2 to see if it still does that, but the build is
taking forever since I'm also testing some ARM code and gdb
5.1.1 is using 50% of the CPU waiting for the target to stop. :)
Anybody else seen this?
--
Grant Edwards
grante@visi.com
next reply other threads:[~2002-07-11 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 15:55 Grant Edwards [this message]
2002-07-11 16:40 ` Grant Edwards
2002-07-11 16:53 ` Keith Seitz
2002-07-11 17:28 ` Grant Edwards
2002-07-12 8:23 ` Grant Edwards
2002-07-12 11:03 ` Grant Edwards
2002-07-11 17:44 Dan Kegel
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=20020711175854.A29971@visi.com \
--to=grante@visi.com \
--cc=gdb@sources.redhat.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