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/testsuite/gdb.cp/ena-dis-br-range.exp | |
| 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/testsuite/gdb.cp/ena-dis-br-range.exp')
| -rw-r--r-- | gdb/testsuite/gdb.cp/ena-dis-br-range.exp | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/gdb/testsuite/gdb.cp/ena-dis-br-range.exp b/gdb/testsuite/gdb.cp/ena-dis-br-range.exp index 782756e..83c9838 100644 --- a/gdb/testsuite/gdb.cp/ena-dis-br-range.exp +++ b/gdb/testsuite/gdb.cp/ena-dis-br-range.exp @@ -44,10 +44,10 @@ proc make_info_breakpoint_reply_re {b1 b2 b21 b22 b23 b24} { "1${ws}breakpoint keep ${b1}${ws}.* in marker\\(\\) at .*" \ "${ws}breakpoint already hit 1 time.*" \ "2${ws}breakpoint${ws}keep${ws}${b2}${ws}<MULTIPLE>.*" \ - "2.1${ws}${b21}.*" \ - "2.2${ws}${b22}.*" \ - "2.3${ws}${b23}.*" \ - "2.4${ws}${b24}.*" \ + "2.1${ws}${b21}${ws}.*" \ + "2.2${ws}${b22}${ws}.*" \ + "2.3${ws}${b23}${ws}.*" \ + "2.4${ws}${b24}${ws}.*" \ ] } @@ -74,18 +74,18 @@ proc test_enable_disable {cmd b1 b2 b21 b22 b23 b24} { test_enable_disable "disable 1" n y y y y y test_enable_disable "enable 1" y y y y y y -# Check that we can disable/disable a breakpoint with multiple +# Check that we can disable/enable a breakpoint with multiple # locations. -test_enable_disable "disable 2" y n y y y y -test_enable_disable "enable 2" y y y y y y +test_enable_disable "disable 2" y n y- y- y- y- +test_enable_disable "enable 2" y y y y y y -# Check that we can disable/disable a range of breakpoints. -test_enable_disable "disable 1-2" n n y y y y -test_enable_disable "enable 1-2" y y y y y y +# Check that we can disable/enable a range of breakpoints. +test_enable_disable "disable 1-2" n n y- y- y- y- +test_enable_disable "enable 1-2" y y y y y y -# Check that we can disable/disable a list of breakpoints. -test_enable_disable "disable 1 2" n n y y y y -test_enable_disable "enable 1 2" y y y y y y +# Check that we can disable/enable a list of breakpoints. +test_enable_disable "disable 1 2" n n y- y- y- y- +test_enable_disable "enable 1 2" y y y y y y # Check that we can disable/enable a single location breakpoint. test_enable_disable "disable 2.2" y y y n y y @@ -100,7 +100,7 @@ test_enable_disable "enable 2.2-3" y y y y y y test_enable_disable "disable 2.2-2" y y y n y y test_enable_disable "enable 2.2-2" y y y y y y -# Check that we can disable/disable a list of breakpoints that +# Check that we can disable/enable a list of breakpoints that # includes some elements with location ranges and others without. test_enable_disable "disable 1 2.1 2.3-4" n y n y n n test_enable_disable "enable 1 2.1 2.3-4" y y y y y y |