From: Daniel Jacobowitz <drow@false.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: gdb@sources.redhat.com
Subject: Re: huge remote debug traffic with multi-thread program
Date: Thu, 17 Feb 2005 01:42:00 -0000 [thread overview]
Message-ID: <20050216165909.GA11396@nevyn.them.org> (raw)
In-Reply-To: <20050216.210432.15259170.nemoto@toshiba-tops.co.jp>
On Wed, Feb 16, 2005 at 09:04:32PM +0900, Atsushi Nemoto wrote:
> When I typed Ctrl-C and 'c' (continue) on gdb, traffic between gdb and
> gdbserver start eating network bandwidth and gdbserver eats whole CPU
> power on the target. Is this a normal behavior?
The normal cause of this sort of problem is GDB's lame software
single-step support. You have two threads iterating in the same piece
of code, and probably GDB is continually getting a trap from the wrong
one. Or it may get confused about where it has put the breakpoint.
Does the problem go away if each thread is in a separate identical copy
of the function?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-02-16 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 16:24 Atsushi Nemoto
2005-02-17 1:42 ` Daniel Jacobowitz [this message]
2005-02-17 9:01 ` Atsushi Nemoto
2005-02-18 22:54 ` Atsushi Nemoto
2005-02-22 18:59 ` Atsushi Nemoto
2005-03-17 5:43 ` Atsushi Nemoto
2005-03-17 11:38 ` Bob Rossi
2005-03-17 18:21 ` Mark Kettenis
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=20050216165909.GA11396@nevyn.them.org \
--to=drow@false.org \
--cc=anemo@mba.ocn.ne.jp \
--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