diff options
| -rw-r--r-- | gdb/ChangeLog | 5 | ||||
| -rw-r--r-- | gdb/NEWS | 11 | ||||
| -rw-r--r-- | gdb/PROBLEMS | 18 |
3 files changed, 22 insertions, 12 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 7e80f63fd9b..dd11dd28e38 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,10 @@ 2004-07-28 Andrew Cagney <cagney@gnu.org> + * PROBLEMS: Mention threads/1650. + * NEWS: Mention the NPTL fix. + +2004-07-28 Andrew Cagney <cagney@gnu.org> + * cli/cli-decode.c (add_setshow_cmd): Delete function. (add_setshow_cmd_full): Make static. * command.h (add_setshow_cmd, add_setshow_cmd_full): Delete. @@ -5,6 +5,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 d166305722b..8cdfe324756 100644 --- a/gdb/PROBLEMS +++ b/gdb/PROBLEMS @@ -126,15 +126,9 @@ sensitive to the operating system and thread library. 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. +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. |