mirrors/binutils-gdb
1
0
Fork 0
mirror of https://sourceware.org/git/binutils-gdb.git synced 2024-11-23 10:03:47 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

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

Browse Source 
* PROBLEMS: Mention threads/1650.
	* NEWS: Mention the NPTL fix.
This commit is contained in:
Andrew Cagney 2004-07-28 19:53:39 +00:00
parent b3f4233622
commit 0dea24683a
3 changed files with 21 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/ChangeLog
View File

@ -1,3 +1,8 @@
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.

11
gdb/NEWS
View File

@ -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

16
gdb/PROBLEMS
View File

@ -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:
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.
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.
This problem does not occur on newer systems that use the NPTL
library, and did not occur with GDB 6.1.