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

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

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 34a331aae80b5f76c7d4e034615932d6db2fae20..8d41b7b3296e0e8828f85b22b8e02972318b2839 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2004-07-26  Michael Chastain  <mec.gnu@mindspring.com>
+
+       Document PR threads/1650.
+       * PROBLEMS (Threads): Document problem with many threads
+
 2004-07-26  Andrew Cagney  <cagney@gnu.org>
 
        * gdb-mi.el: Move from here ...

diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 1fa353838c7f5653c687ab9305c43d126fae7d35..d166305722b1c62eb55d441cc07cd131235ff5f9 100644 (file)
--- a/gdb/PROBLEMS
+++ b/gdb/PROBLEMS
@@ -121,3 +121,20 @@ gdb/1505: [regression] gdb prints a bad backtrace for a thread
 When backtracing a thread, gdb does not stop when it reaches the
 outermost frame, instead continuing until it hits garbage.  This is
 sensitive to the operating system and thread library.
+
+*** 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.