diff options
| author | Andrew Cagney <cagney@redhat.com> | 2004-07-28 19:51:42 +0000 |
|---|---|---|
| committer | Andrew Cagney <cagney@redhat.com> | 2004-07-28 19:51:42 +0000 |
| commit | 72811a1657a0603be0d59ab293a344c911e32037 (patch) | |
| tree | 34cbcdeb81e351349d60f4421f5732e1597d0ce8 | |
| parent | 5c784590f496a0107a86d57ae00417615c4f8ea0 (diff) | |
| download | gdb-72811a1657a0603be0d59ab293a344c911e32037.tar.gz | |
2004-07-28 Andrew Cagney <cagney@gnu.org>
* PROBLEMS: Mention threads/1650.
* NEWS: Mention the NPTL fix.
| -rw-r--r-- | gdb/NEWS | 11 | ||||
| -rw-r--r-- | gdb/PROBLEMS | 11 |
2 files changed, 22 insertions, 0 deletions
@@ -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. |