diff options
| author | Pedro Alves <pedro@palves.net> | 2022-05-24 19:30:10 +0100 |
|---|---|---|
| committer | Pedro Alves <pedro@palves.net> | 2022-05-25 19:51:46 +0100 |
| commit | fbcda577011d73fdcf1ebf86160b6fc8ddd95299 (patch) | |
| tree | f9a7342f657fa0088f45eb6ae03899223f242235 /gdb/doc | |
| parent | 3ac9da49378ccb061e3e33e4342c35949bf368a9 (diff) | |
| download | gdb-fbcda577011d73fdcf1ebf86160b6fc8ddd95299.zip gdb-fbcda577011d73fdcf1ebf86160b6fc8ddd95299.tar.gz gdb-fbcda577011d73fdcf1ebf86160b6fc8ddd95299.tar.bz2 | |
Show enabled locations with disabled breakpoint parent as "y-"
Currently, breakpoint locations that are enabled while their parent
breakpoint is disabled are displayed with "y" in the Enb colum of
"info breakpoints":
(gdb) info breakpoints
Num Type Disp Enb Address What
1 breakpoint keep n <MULTIPLE>
1.1 y 0x00000000000011b6 in ...
1.2 y 0x00000000000011c2 in ...
1.3 n 0x00000000000011ce in ...
Such locations won't trigger a break, so to avoid confusion, show "y-"
instead. For example:
(gdb) info breakpoints
Num Type Disp Enb Address What
1 breakpoint keep n <MULTIPLE>
1.1 y- 0x00000000000011b6 in ...
1.2 y- 0x00000000000011c2 in ...
1.3 n 0x00000000000011ce in ...
The "-" sign is inspired on how the TUI represents breakpoints on the
left side of the source window, with "b-" for a disabled breakpoint.
Change-Id: I9952313743c51bf21b4b380c72360ef7d4396a09
Diffstat (limited to 'gdb/doc')
| -rw-r--r-- | gdb/doc/gdb.texinfo | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index e5c1ee3..6867998 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -4668,6 +4668,19 @@ in which case @value{GDBN} acts on all the locations in the range (inclusive). Disabling or enabling the parent breakpoint (@pxref{Disabling}) affects all of the locations that belong to that breakpoint. +Locations that are enabled while their parent breakpoint is disabled +won't trigger a break, and are denoted by @code{y-} in the @code{Enb} +column. For example: + +@smallexample +(@value{GDBP}) info breakpoints +Num Type Disp Enb Address What +1 breakpoint keep n <MULTIPLE> +1.1 y- 0x00000000000011b6 in ... +1.2 y- 0x00000000000011c2 in ... +1.3 n 0x00000000000011ce in ... +@end smallexample + @cindex pending breakpoints It's quite common to have a breakpoint inside a shared library. Shared libraries can be loaded and unloaded explicitly, |