This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: huge remote debug traffic with multi-thread program
- From: Daniel Jacobowitz <drow at false dot org>
- To: Atsushi Nemoto <anemo at mba dot ocn dot ne dot jp>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 16 Feb 2005 11:59:09 -0500
- Subject: Re: huge remote debug traffic with multi-thread program
- References: <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