From: teawater <teawater@gmail.com>
To: "N. van Bolhuis" <nvbolhuis@aimvalley.nl>
Cc: gdb@sourceware.org
Subject: Re: gdb doesn't show all threads, but gdbserver does
Date: Tue, 20 Jan 2009 00:21:00 -0000 [thread overview]
Message-ID: <daef60380901191621v4b9c5450k4518c8eb8804a694@mail.gmail.com> (raw)
In-Reply-To: <4974EBFF.307@aimvalley.nl>
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 <nvbolhuis@aimvalley.nl> 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
> threads.
>
> 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).
>
>
>
next prev parent reply other threads:[~2009-01-20 0:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 21:09 N. van Bolhuis
2009-01-20 0:21 ` teawater [this message]
2009-01-20 7:28 ` Norbert van Bolhuis
2009-01-20 18:37 ` Paul Pluzhnikov
2009-01-20 20:18 ` N. van Bolhuis
2009-01-20 20:36 ` Paul Pluzhnikov
2009-01-20 21:17 ` N. van Bolhuis
2009-01-20 22:24 ` Andreas Schwab
2009-01-20 22:45 ` Paul Pluzhnikov
2009-01-21 0:10 ` teawater
2009-01-21 10:32 ` Norbert van Bolhuis
2009-01-21 11:24 ` teawater
2009-01-21 13:45 ` teawater
2009-01-21 16:41 ` Paul Pluzhnikov
2009-02-12 3:08 ` teawater
2009-02-12 3:08 ` teawater
2009-01-21 0:05 ` teawater
2009-01-21 0:14 ` Paul Pluzhnikov
2009-01-21 0:26 ` teawater
2009-01-21 2:35 ` teawater
2009-01-21 4:16 ` Daniel Jacobowitz
2009-01-21 7:14 ` teawater
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=daef60380901191621v4b9c5450k4518c8eb8804a694@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@sourceware.org \
--cc=nvbolhuis@aimvalley.nl \
/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