Re: gdb doesn't show all threads, but gdbserver does

[Paul Pluzhnikov <ppluzhnikov@google.com>]

I just updated the wiki ...

On Wed, Jan 21, 2009 at 5:45 AM, teawater <teawater@gmail.com> wrote:
> My mean is maybe you can update this question and answer to FAQ in wiki. :)
>
> On Wed, Jan 21, 2009 at 19:24, teawater <teawater@gmail.com> wrote:
>> What about FAQ?
>>
>> On Wed, Jan 21, 2009 at 18:32, Norbert van Bolhuis
>> <nvbolhuis@aimvalley.nl> wrote:
>>>
>>> Paul Pluzhnikov 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.
>>>>
>>>
>>> I consulted the GDB manual first, then google.
>>>
>>> http://sourceware.org/gdb/wiki is an interesting source of information.
>>> I expect to see this common mistake being mentioned there, but I can't
>>> find it.
>>>
>>> Anyway, thanks to everybody for all answers.
>>>
>>>
>>
>



-- 
Paul Pluzhnikov