diff options
| author | Andrew Burgess <aburgess@redhat.com> | 2023-07-07 16:36:26 +0100 |
|---|---|---|
| committer | Andrew Burgess <aburgess@redhat.com> | 2023-07-10 10:49:59 +0100 |
| commit | 3f3ffaca04967511fa14b5cb6ee4cd1ae3802c39 (patch) | |
| tree | 60388b35e1c37a66f99d291a4265064c693ebbff /gdb/testsuite/gdb.compile | |
| parent | c432a27df338c6720303c29eab18467cfc981cb8 (diff) | |
| download | gdb-3f3ffaca04967511fa14b5cb6ee4cd1ae3802c39.zip gdb-3f3ffaca04967511fa14b5cb6ee4cd1ae3802c39.tar.gz gdb-3f3ffaca04967511fa14b5cb6ee4cd1ae3802c39.tar.bz2 | |
gdb: include location number in breakpoint error message
This commit improves the output of this previous commit:
commit 2dc3457a454a35d0617dc1f9cc1db77468471f95
Date: Fri Oct 14 13:22:55 2022 +0100
gdb: include breakpoint number in testing condition error message
The earlier commit extended the error message:
Error in testing breakpoint condition:
to include the breakpoint number, e.g.:
Error in testing breakpoint condition 3:
This commit extends takes this further, and includes the location
number if the breakpoint has multiple locations, so we might now see:
Error in testing breakpoint condition 3.2:
Just as with how GDB reports a normal breakpoint stop, if a breakpoint
only has a single location then the location number is not included,
this keeps things nice and consistent.
I've extended one of the tests to cover the new functionality.
Approved-By: Pedro Alves <pedro@palves.net>
Diffstat (limited to 'gdb/testsuite/gdb.compile')
0 files changed, 0 insertions, 0 deletions