OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* NEWS: Mention libthread_db debugging with core files.

This commit is contained in:
Pedro Alves 2010-08-26 19:47:23 +00:00
parent fd4679698a
commit ae53ffa4b6
2 changed files with 29 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/ChangeLog
View File

@ -1,3 +1,7 @@
2010-08-26 Pedro Alves <pedro@codesourcery.com>
* NEWS: Mention libthread_db debugging with core files.
2010-08-26 Doug Evans <dje@google.com>
* dwarf2read.c (dwarf2_build_include_psymtabs): Remove unnecessary

25
gdb/NEWS
View File

@ -37,6 +37,31 @@
expression. Such a watchpoint is never deleted due to it going out
of scope.
* GDB now supports thread debugging of core dumps on GNU/Linux.
GDB now activates thread debugging using the libthread_db library
when debugging GNU/Linux core dumps, similarly to when debugging
live processes. As a result, when debugging a core dump file, GDB
is now able to display pthread_t ids of threads. For example, "info
threads" shows the same output as when debugging the process when it
was live. In earlier releases, you'd see something like this:
(gdb) info threads
* 1 LWP 6780 main () at main.c:10
While now you see this:
(gdb) info threads
* 1 Thread 0x7f0f5712a700 (LWP 6780) main () at main.c:10
It is also now possible to inspect TLS variables when debugging core
dumps.
When debugging a core dump generated on a machine other than the one
used to run GDB, you may need to point GDB at the correct
libthread_db library with the "set libthread-db-search-path"
command. See the user manual for more details on this command.
*** Changes in GDB 7.2
* Shared library support for remote targets by default