Re: [rfa/PROBLEMS] document threads/1650, thread internal error

[Andrew Cagney <cagney@gnu.org>]

> Argh, I should have read to the end of my mailbox before committing
> to gdb HEAD.
> 
> 
>>> - that it is (to the best of our knowledge) GNU/Linux and LinuxThreads 
>>> specific
> 
> 
> Good question, but your answer is wrong.

Outch!

> Looking at gdb-testers@ for
> June and July, I see that hppa2.0w-hp-hpux11.00 and
> ia64-unknown-linux-gnu have this problem.  Many other arches can't
> compile manythreads.c so we can't tell either way.

I thought HP/UX threads are pretty much busted anyway.  Since it isn't a 
LinuxThreads / libthread_db system, I'd assume (with out strong evidence 
to the contrary) that the testsuite failure is due to a bug in the HP/UX 
code.

>>> So the closing paragraph should make this clearer.  Something like 
>>> ``This problem has not been observed on GNU/Linux systems that use NPTL 
>>> (New Posix Threads Library[?]). People still using linuxthreads are 
>>> strongly encouraged to migrate to NPTL''.
> 
> 
> Shouldn't that be in NEWS?  Maybe I've missed some discussion,
> but it's news to me that users linuxthreads are encouraged to
> switch.

It's our workaround to a problem.

>>> We should also mention that on GNU/Linux NPTL based systems a problem 
>>> with GDB loosing track of threads was fixed.
> 
> 
> That sounds good.

Andrew