This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [rfa/PROBLEMS] document threads/1650, thread internal error
- From: Andrew Cagney <cagney at gnu dot org>
- To: Michael Chastain <mec dot gnu at mindspring dot com>
- Cc: eliz at gnu dot org, gdb-patches at sources dot redhat dot com
- Date: Mon, 26 Jul 2004 15:51:16 -0400
- Subject: Re: [rfa/PROBLEMS] document threads/1650, thread internal error
- References: <20040726154838.4E0E44B104@berman.michael-chastain.com>
+
+ *** Threads
+
+ threads/1650: manythreads.exp
+
+ A program which creates many threads which exit very quickly (hundreds
+ of thousands of threads in the test program) can cause gdb to generate
+ an internal error. The internal error often looks like:
+
+ lin-lwp.c:744: internal-error: stop_callback: Assertion `lp->status == 0' failed.
+ A problem internal to GDB has been detected.
+ further debugging may prove unreliable.
+ Quit this debugging session? (y or n)
+
+ This has been observed on native i686-pc-linux-gnu with linuxthreads,
+ the old threading model. With NPTL threads, this internal error has not
+ been observed.
+
I think it more clearly needs to convey the following information:
- that it is (to the best of our knowledge) GNU/Linux and LinuxThreads
specific
So the opening sentence should mention both of those data points.
Something like ``On a GNU/Linux system that uses linuxthreads, a program
....''
- switching to NPTL highly recommended
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''.
We should also mention that on GNU/Linux NPTL based systems a problem
with GDB loosing track of threads was fixed.
Andrew