From: "N. van Bolhuis" <nvbolhuis@aimvalley.nl>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: teawater <teawater@gmail.com>, gdb@sourceware.org
Subject: Re: gdb doesn't show all threads, but gdbserver does
Date: Tue, 20 Jan 2009 20:18:00 -0000 [thread overview]
Message-ID: <49763169.8070208@aimvalley.nl> (raw)
In-Reply-To: <8ac60eac0901201037t71b6bd62j8668bd004e933f53@mail.gmail.com>
Paul Pluzhnikov wrote:
> On Mon, Jan 19, 2009 at 11:28 PM, Norbert van Bolhuis
> <nvbolhuis@aimvalley.nl> wrote:
>
>> # cat /proc/920/status
>
> What did you hope to find from status?
>
proof that 7 threads are really there.
> What you really want is /proc/919/maps: this will show whether
> libthread_db.so.1 was loaded into gdb, and if so, which one.
>
> It should be the same as the one which shows up in
> 'ldd gdbserver' output.
>
In fact I did just that. I didn't mention it since it's there
(libthread_db.so.1 is loaded into gdb) so this is not the issue.
next prev parent reply other threads:[~2009-01-20 20:18 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
2009-01-20 7:28 ` Norbert van Bolhuis
2009-01-20 18:37 ` Paul Pluzhnikov
2009-01-20 20:18 ` N. van Bolhuis [this message]
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=49763169.8070208@aimvalley.nl \
--to=nvbolhuis@aimvalley.nl \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.com \
--cc=teawater@gmail.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