* NEWS: Mention libthread_db debugging with core files.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 4452357ef113642a46ee9fcde9290571efe36de9..7404327d1b006c5309b38ce9d60401c1b49221e2 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -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

diff --git a/gdb/NEWS b/gdb/NEWS
index 5b16c260afe8d1e014bd9f4715ca293ec446367d..b38399894d20edbf00cb674c4bf91f2977e2fda2 100644 (file)
--- 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