This is the mail archive of the
mailing list for the GDB project.
Re: gdb doesn't show all threads, but gdbserver does
- From: teawater <teawater at gmail dot com>
- To: "N. van Bolhuis" <nvbolhuis at aimvalley dot nl>
- Cc: gdb at sourceware dot org
- Date: Tue, 20 Jan 2009 08:21:41 +0800
- Subject: Re: gdb doesn't show all threads, but gdbserver does
- References: <4974EBFF.firstname.lastname@example.org>
Both gdbserver and gdb use libthread_db.
gdbserver link together with the lib.
gdb dlopen the lib when it need it.
So I think maybe gdb didn't find the lib or something else. Do you gdb
have some error message?
On Tue, Jan 20, 2009 at 05:09, N. van Bolhuis <email@example.com> wrote:
> I built a gdb (v6.8) for powerpc to be executed on powerpc target
> (This GDB was configured as "powerpc-e300c3-linux"...).
> If I use this target gdb to debug my powerpc program and hit a
> breakpoint "info threads" shows only one thread.
> This is incorrect since there are 7 threads (cat /proc/<pid>/status
> shows 7 threads).
> If I debug the same program using gdbserver on target and gdb on a host=i686 (This GDB was configured as "--host=i686-linux
> --target=powerpc-e300c3-linux"...) "info threads" shows the expected 7
> How can this be ?
> (I noticed the target gdbserver needs libthread_db.so.1, the target gdb
> does not. Maybe this is what's causing this).