From: Pedro Alves Date: Thu, 26 Aug 2010 19:47:23 +0000 (+0000) Subject: * NEWS: Mention libthread_db debugging with core files. X-Git-Tag: sid-snapshot-20100901~60 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=ae53ffa4b631eede55fa98f7b27050d54024c575;p=external%2Fbinutils.git * NEWS: Mention libthread_db debugging with core files. --- diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 4452357..7404327 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2010-08-26 Pedro Alves + + * NEWS: Mention libthread_db debugging with core files. + 2010-08-26 Doug Evans * dwarf2read.c (dwarf2_build_include_psymtabs): Remove unnecessary diff --git a/gdb/NEWS b/gdb/NEWS index 5b16c26..b383998 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -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