Files
binutils-gdb/gdb/testsuite/gdb.base/hw-sw-break-same-address.exp
Andrew Burgess 1d506c26d9 Update copyright year range in header of all files managed by GDB
This commit is the result of the following actions:

  - Running gdb/copyright.py to update all of the copyright headers to
    include 2024,

  - Manually updating a few files the copyright.py script told me to
    update, these files had copyright headers embedded within the
    file,

  - Regenerating gdbsupport/Makefile.in to refresh it's copyright
    date,

  - Using grep to find other files that still mentioned 2023.  If
    these files were updated last year from 2022 to 2023 then I've
    updated them this year to 2024.

I'm sure I've probably missed some dates.  Feel free to fix them up as
you spot them.
2024-01-12 15:49:57 +00:00

71 lines
2.2 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/>.
# Test that inserting a hardware and a software breakpoint at the same
# address behaves as expected. GDB used to consider hw and sw
# breakpoint locations as duplicate locations, which would lead to bad
# behavior. See PR gdb/25741.
require allow_hw_breakpoint_tests
set test hbreak
set srcfile ${test}.c
if { [prepare_for_testing "failed to prepare" ${test} ${srcfile}] } {
return -1
}
if ![runto_main] {
return -1
}
delete_breakpoints
gdb_test_no_output "set breakpoint always-inserted on"
gdb_test_no_output "set breakpoint condition-evaluation host"
gdb_test_no_output "set confirm off"
# Test inserting a hw breakpoint first, then a sw breakpoint at the
# same address.
with_test_prefix "hw-sw" {
gdb_test "hbreak -q main" \
"Hardware assisted breakpoint .* at .*" \
"hbreak"
gdb_test "break -q main" \
"Note: breakpoint .* also set at .*\r\nBreakpoint .* at .*" \
"break"
# A bad GDB debugging against GDBserver would output a warning
# here:
# delete breakpoints
# warning: error removing breakpoint 3 at <ADDRESS>
# (gdb) FAIL: gdb.base/hw-sw-break-same-address.exp: hw-sw: delete breakpoints
gdb_test_no_output "delete breakpoints"
}
# Now the opposite: test inserting a sw breakpoint first, then a hw
# breakpoint at the same address.
with_test_prefix "sw-hw" {
gdb_test "break -q main" \
"Breakpoint .* at .*" \
"break"
gdb_test "hbreak -q main" \
"Note: breakpoint .* also set at .*\r\nHardware assisted breakpoint .* at .*" \
"hbreak"
gdb_test_no_output "delete breakpoints"
}