This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb doesn't show all threads, but gdbserver does
- From: teawater <teawater at gmail dot com>
- To: Paul Pluzhnikov <ppluzhnikov at google dot com>
- Cc: Andreas Schwab <schwab at suse dot de>, "N. van Bolhuis" <nvbolhuis at aimvalley dot nl>, gdb at sourceware dot org
- Date: Thu, 12 Feb 2009 11:07:47 +0800
- Subject: Re: gdb doesn't show all threads, but gdbserver does
- References: <4974EBFF.307@aimvalley.nl> <daef60380901191621v4b9c5450k4518c8eb8804a694@mail.gmail.com> <49757D1C.7010309@aimvalley.nl> <8ac60eac0901201037t71b6bd62j8668bd004e933f53@mail.gmail.com> <49763169.8070208@aimvalley.nl> <8ac60eac0901201236i2d3a266akaa673cd12a4ec7cb@mail.gmail.com> <49763F67.5010009@aimvalley.nl> <je1vux7h08.fsf@sykes.suse.de> <8ac60eac0901201445m4d85d30k5b5fc87783208a32@mail.gmail.com>
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
>