From: teawater <teawater@gmail.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Andreas Schwab <schwab@suse.de>,
"N. van Bolhuis" <nvbolhuis@aimvalley.nl>,
gdb@sourceware.org
Subject: Re: gdb doesn't show all threads, but gdbserver does
Date: Thu, 12 Feb 2009 03:08:00 -0000 [thread overview]
Message-ID: <daef60380902111908y14a423ebma3b8cdfb449e05d9@mail.gmail.com> (raw)
In-Reply-To: <daef60380902111907t22f761a8xb9adacd96f1f721a@mail.gmail.com>
http://sourceware.org/ml/gdb-patches/2009-02/msg00232.html
On Thu, Feb 12, 2009 at 11:07, teawater <teawater@gmail.com> wrote:
> I make a patch to output a warning.
> http://sourceware.org/ml/gdb-patches/2009-02/msg00234.html
>
> Thanks,
> Hui
>
> On Wed, Jan 21, 2009 at 06:45, Paul Pluzhnikov <ppluzhnikov@google.com> wrote:
>> On Tue, Jan 20, 2009 at 2:24 PM, Andreas Schwab <schwab@suse.de> wrote:
>>
>>> It's actually libthread_db that needs a non-global symbol from
>>> libpthread.
>>
>> IOW, it's a glibc feature :)
>>
>> Stripping libpthread appears to be a very common mistake:
>>
>> - we've seen it twice on this list in the last two weeks,
>> - I made it myself 4 weeks ago, even though I *knew* that libpthread
>> must not be stripped.
>>
>> I wonder if we should warn glibc users? Something like:
>>
>> Warning: your /lib64/libpthread.so.0 has been stripped.
>> GDB will not see other threads, and multithreaded debugging will
>> be unreliable.
>> See http://sourceware.org/gdb/wiki/... for further info.
>>
>> --
>> Paul Pluzhnikov
>>
>
next prev parent reply other threads:[~2009-02-12 3:08 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
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 [this message]
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=daef60380902111908y14a423ebma3b8cdfb449e05d9@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@sourceware.org \
--cc=nvbolhuis@aimvalley.nl \
--cc=ppluzhnikov@google.com \
--cc=schwab@suse.de \
/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