aboutsummaryrefslogtreecommitdiff
path: root/gdb/NEWS
diff options
context:
space:
mode:
Diffstat (limited to 'gdb/NEWS')
-rw-r--r--gdb/NEWS26
1 files changed, 26 insertions, 0 deletions
diff --git a/gdb/NEWS b/gdb/NEWS
index 424e5ff..dddef65 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -81,6 +81,26 @@
* New convenience variable $_inferior_thread_count contains the number
of live threads in the current inferior.
+* When a breakpoint with multiple code locations is hit, GDB now prints
+ the code location using the syntax <breakpoint_number>.<location_number>
+ such as in:
+ Thread 1 "zeoes" hit Breakpoint 2.3, some_func () at zeoes.c:8
+
+* When a breakpoint is hit, GDB now sets the convenience variables $_hit_bpnum
+ and $_hit_locno to the hit breakpoint number and code location number.
+ This allows to disable the last hit breakpoint using
+ (gdb) disable $_hit_bpnum
+ or disable only the specific breakpoint code location using
+ (gdb) disable $_hit_bpnum.$_hit_locno
+ These commands can be used inside the command list of a breakpoint to
+ automatically disable the just encountered breakpoint (or the just
+ encountered specific breakpoint code location).
+ When a breakpoint has only one location, $_hit_locno is set to 1 so that
+ (gdb) disable $_hit_bpnum.$_hit_locno
+ and
+ (gdb) disable $_hit_bpnum
+ are both disabling the breakpoint.
+
* New commands
maintenance set ignore-prologue-end-flag on|off
@@ -152,6 +172,12 @@ GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
GNU/Linux/CSKY (gdbserver) csky*-*linux*
+* MI changes
+
+ ** The async record stating the stopped reason 'breakpoint-hit' now
+ contains an optional field locno giving the code location number
+ when the breakpoint has multiple code locations.
+
* Python API
** GDB will now reformat the doc string for gdb.Command and