forked from Imagelibrary/binutils-gdb
4a4fd10d17
The output of "info breakpoints" includes breakpoint, watchpoint, tracepoint, and catchpoint if they are created, so it should show all the four types are deleted in the output of "info breakpoints" to report empty list after "delete breakpoints". It should also change the output of "delete breakpoints" to make it clear that watchpoints, tracepoints, and catchpoints are also being deleted. This is suggested by Guinevere Larsen, thank you. $ make check-gdb TESTS="gdb.base/access-mem-running.exp" $ gdb/gdb gdb/testsuite/outputs/gdb.base/access-mem-running/access-mem-running [...] (gdb) break main Breakpoint 1 at 0x12000073c: file /home/loongson/gdb.git/gdb/testsuite/gdb.base/access-mem-running.c, line 32. (gdb) watch global_counter Hardware watchpoint 2: global_counter (gdb) trace maybe_stop_here Tracepoint 3 at 0x12000071c: file /home/loongson/gdb.git/gdb/testsuite/gdb.base/access-mem-running.c, line 27. (gdb) catch fork Catchpoint 4 (fork) (gdb) info breakpoints Num Type Disp Enb Address What 1 breakpoint keep y 0x000000012000073c in main at /home/loongson/gdb.git/gdb/testsuite/gdb.base/access-mem-running.c:32 2 hw watchpoint keep y global_counter 3 tracepoint keep y 0x000000012000071c in maybe_stop_here at /home/loongson/gdb.git/gdb/testsuite/gdb.base/access-mem-running.c:27 not installed on target 4 catchpoint keep y fork Without this patch: (gdb) delete breakpoints Delete all breakpoints? (y or n) y (gdb) info breakpoints No breakpoints or watchpoints. (gdb) info breakpoints 3 No breakpoint or watchpoint matching '3'. With this patch: (gdb) delete breakpoints Delete all breakpoints, watchpoints, tracepoints, and catchpoints? (y or n) y (gdb) info breakpoints No breakpoints, watchpoints, tracepoints, or catchpoints. (gdb) info breakpoints 3 No breakpoint, watchpoint, tracepoint, or catchpoint matching '3'. Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn> Approved-by: Kevin Buettner <kevinb@redhat.com> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
61 lines
2.6 KiB
Plaintext
61 lines
2.6 KiB
Plaintext
# Copyright 2020-2024 Free Software Foundation, Inc.
|
|
|
|
# This program is free software; you can redistribute it and/or modify
|
|
# it under the terms of the GNU General Public License as published by
|
|
# the Free Software Foundation; either version 3 of the License, or
|
|
# (at your option) any later version.
|
|
#
|
|
# This program is distributed in the hope that it will be useful,
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
# GNU General Public License for more details.
|
|
#
|
|
# You should have received a copy of the GNU General Public License
|
|
# along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
# Check for an issue in GDB where buildsym_compunit::record_line was
|
|
# removing duplicate line table entries, but skip_prologue_using_sal
|
|
# depends on these duplicates to spot the end of the prologue.
|
|
#
|
|
# When the de-duplication was added this regression was not spotted as
|
|
# it requires a particular combination of a (very) small function
|
|
# being inlined into an also very small outer function.
|
|
#
|
|
# See also gdb.dwarf/dw2-inline-small-func.exp for a version of this
|
|
# test that makes use of the Dejagnu DWARF compiler.
|
|
#
|
|
# This test simply compiles with optimization and checks that GDB can
|
|
# do something suitable with the compiled binary. Problems with this
|
|
# test are most likely to occur when GDB asks the target specific code
|
|
# to skip the prologue (gdbarch_skip_prologue). Some targets make use
|
|
# of skip_prologue_using_sal, which should be fine, however, some
|
|
# targets make a poor attempt to duplicate parts of
|
|
# skip_prologue_using_sal, these targets could easily fail this test.
|
|
# This is not (necessarily) a problem with this test, but could
|
|
# indicate a weakness with the target in question.
|
|
|
|
standard_testfile inline-small-func.c inline-small-func.h
|
|
|
|
if { [prepare_for_testing "failed to prepare" ${testfile} \
|
|
[list $srcfile] {debug optimize=-O1}] } {
|
|
return -1
|
|
}
|
|
|
|
if ![runto_main] {
|
|
return -1
|
|
}
|
|
|
|
# Delete all breakpoints, watchpoints, tracepoints, and catchpoints so that
|
|
# the output of "info breakpoints" below will only contain a single breakpoint.
|
|
delete_breakpoints
|
|
|
|
# Place a breakpoint within the function in the header file.
|
|
set linenum [gdb_get_line_number "callee: body" $srcfile2]
|
|
gdb_breakpoint "${srcfile2}:${linenum}"
|
|
|
|
# Check that the breakpoint was placed where we expected. It should
|
|
# appear at the requested line. When the bug in GDB was present the
|
|
# breakpoint would be placed on one of the following lines instead.
|
|
gdb_test "info breakpoints" \
|
|
".* in callee at \[^\r\n\]+${srcfile2}:${linenum}\\y.*"
|