summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Cagney <cagney@redhat.com>2004-07-28 19:51:42 +0000
committerAndrew Cagney <cagney@redhat.com>2004-07-28 19:51:42 +0000
commit97f7403fb3a2c826fe76886e48593d0dc469d112 (patch)
treef70da1a34accc2b6cc40b2e854c608088abcba3d
parent38c279e41439e2fc68892fad3a3cc59a3a9098ba (diff)
downloadbinutils-gdb-97f7403fb3a2c826fe76886e48593d0dc469d112.tar.gz
2004-07-28 Andrew Cagney <cagney@gnu.org>
* PROBLEMS: Mention threads/1650. * NEWS: Mention the NPTL fix.
-rw-r--r--gdb/ChangeLog5
-rw-r--r--gdb/NEWS11
-rw-r--r--gdb/PROBLEMS11
3 files changed, 27 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 4e7e41cdd35..956a87218c1 100644
--- 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 9c5f87e5d0e..75995a5bb9c 100644
--- 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 1fa353838c7..8cdfe324756 100644
--- 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.