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

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

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 4e7e41cdd35c94ffb565aa8b481b19106d45a7a3..956a87218c18bc15f670c77773611a4c613d230b 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2004-07-28  Andrew Cagney  <cagney@gnu.org>
+
+       * PROBLEMS: Mention threads/1650.
+       * NEWS: Mention the NPTL fix.
+
 2004-07-26  Andrew Cagney  <cagney@gnu.org>
 
        * gdb-mi.el: Move from here ...

diff --git a/gdb/NEWS b/gdb/NEWS
index 9c5f87e5d0efc510a4c0620781e55113493427f5..75995a5bb9ce3d4a440b72286373144ab0ebf1f2 100644 (file)
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -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

diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 1fa353838c7f5653c687ab9305c43d126fae7d35..8cdfe324756ed61eb8ed38fb7c46a9014a326dd6 100644 (file)
--- a/gdb/PROBLEMS
+++ b/gdb/PROBLEMS
@@ -121,3 +121,14 @@ 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
+
+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.