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

[mec.gnu@mindspring.com (Michael Chastain)]

Here is a PROBLEMS entry for gdb/1650, the internal error on
gdb.threads/manythreads.exp.

Not tested (don't know how to test ascii documentation).  The internal
error still happens with both gdb HEAD and gdb gdb_6_2-branch.  Andrew
says that a set of 30 test runs with NPTL worked fine.

Okay to apply to gdb HEAD?
Okay to apply to gdb gdb_6_2-branch?

Michael C

2004-07-26  Michael Chastain  <mec.gnu@mindspring.com>

	Document PR threads/1650.
	* PROBLEMS (Threads): Document problem with many threads

Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.32
diff -c -3 -p -r1.32 PROBLEMS
*** PROBLEMS	18 Jul 2004 22:29:40 -0000	1.32
--- PROBLEMS	26 Jul 2004 15:44:21 -0000
*************** Fortunately, PowerPC architecture suppor
*** 129,131 ****
--- 129,149 ----
  have been updated.  People encountering problems should consider
  downloading a more current snapshot of GDB
  (http://www.gnu.org/software/gdb/current/).
+ 
+ *** 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.
+