Re: [patch/rfc/6.2] Mention threads in NEWS and PROBLEMS

[Andrew Cagney <cagney at gnu dot org>]

committed per attached,

Andrew
2004-07-28  Andrew Cagney  <cagney@gnu.org>

	* PROBLEMS: Mention threads/1650.
	* NEWS: Mention the NPTL fix.

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.154.2.5
diff -p -u -r1.154.2.5 NEWS
--- NEWS	26 Jul 2004 18:29:13 -0000	1.154.2.5
+++ NEWS	28 Jul 2004 19:50:56 -0000
@@ -3,6 +3,17 @@
 
 *** Changes in GDB 6.2:
 
+* Fix for ``many threads''
+
+On GNU/Linux systems that use the NPTL threads library, a program
+rapidly creating and deleting threads would confuse GDB leading to the
+error message:
+
+	ptrace: No such process.
+	thread_db_get_info: cannot get thread info: generic error
+
+This problem has been fixed.
+
 * "-async" and "-noasync" options removed.
 
 Support for the broken "-noasync" option has been removed (it caused
Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.31.2.3
diff -p -u -r1.31.2.3 PROBLEMS
--- PROBLEMS	26 Jul 2004 18:29:13 -0000	1.31.2.3
+++ PROBLEMS	28 Jul 2004 19:50:56 -0000
@@ -121,3 +121,14 @@ gdb/1505: [regression] gdb prints a bad 
 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
+
+On GNU/Linux systems that use the old LinuxThreads thread library, a
+program rapidly creating and deleting threads can confuse GDB leading
+to an internal error.
+
+This problem does not occur on newer systems that use the NPTL
+library, and did not occur with GDB 6.1.