Fix PR threads/19422 - show which thread caused stop

[deliverable/binutils-gdb.git] / gdb / NEWS

diff --git a/gdb/NEWS b/gdb/NEWS
index 024c184879ec5a689fd34fe1f523366b6762d1ce..f4ba65dfa9d6de04ef5fae98c34341587585f619 100644 (file)
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -22,7 +22,7 @@
 
   GDB now maintains a second thread ID per thread, referred to as the
   global thread ID, which is the new equivalent of thread numbers in
-  previous releases.
+  previous releases.  See also $_gthread below.
 
   For backwards compatibility, MI's thread IDs always refer to global
   IDs.
@@ -34,12 +34,28 @@
      [Switching to thread 2.1 (Thread 0x7ffff7fc2740 (LWP 8157))] (running)
      (gdb)
 
+* In commands that accept a list of thread IDs, you can now refer to
+  all threads of an inferior using a star wildcard.  GDB accepts
+  "INF_NUM.*", to refer to all threads of inferior INF_NUM, and "*" to
+  refer to all threads of the current inferior.  For example, "info
+  threads 2.*".
+
 * You can use "info threads -gid" to display the global thread ID of
   all threads.
 
+* The new convenience variable $_gthread holds the global number of
+  the current thread.
+
 * The new convenience variable $_inferior holds the number of the
   current inferior.
 
+* GDB now displays the ID and name of the thread that hit a breakpoint
+  or received a signal, if your program is multi-threaded.  For
+  example:
+
+   Thread 3 "bar" hit Breakpoint 1 at 0x40087a: file program.c, line 20.
+   Thread 1 "main" received signal SIGINT, Interrupt.
+
 * Record btrace now supports non-stop mode.
 
 * Support for tracepoints on aarch64-linux was added in GDBserver.