FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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> 2004-07-28 Andrew Cagney <cagney@gnu.org>
* cli/cli-decode.c (add_setshow_cmd): Delete function. * cli/cli-decode.c (add_setshow_cmd): Delete function.

11
gdb/NEWS
View file

@ -5,6 +5,17 @@
*** Changes in GDB 6.2: *** 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. * "-async" and "-noasync" options removed.
Support for the broken "-noasync" option has been removed (it caused 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 threads/1650: manythreads.exp
A program which creates many threads which exit very quickly (hundreds On GNU/Linux systems that use the old LinuxThreads thread library, a
of thousands of threads in the test program) can cause gdb to generate program rapidly creating and deleting threads can confuse GDB leading
an internal error. The internal error often looks like: to an internal error.
lin-lwp.c:744: internal-error: stop_callback: Assertion `lp->status == 0' failed. This problem does not occur on newer systems that use the NPTL
A problem internal to GDB has been detected. library, and did not occur with GDB 6.1.
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.