This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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.
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.
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.
We should also mention that on GNU/Linux NPTL based systems a problem with GDB loosing track of threads was fixed.
That sounds good.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |