]> git.ipfire.org Git - thirdparty/binutils-gdb.git/blame - gdb/testsuite/gdb.base/sss-bp-on-user-bp.exp
This is to fix a further problem with merging resource sections. It turns
[thirdparty/binutils-gdb.git] / gdb / testsuite / gdb.base / sss-bp-on-user-bp.exp
CommitLineData
9ba6657a
PA
1# Copyright 2014 Free Software Foundation, Inc.
2
3# This program is free software; you can redistribute it and/or modify
4# it under the terms of the GNU General Public License as published by
5# the Free Software Foundation; either version 3 of the License, or
6# (at your option) any later version.
7#
8# This program is distributed in the hope that it will be useful,
9# but WITHOUT ANY WARRANTY; without even the implied warranty of
10# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
11# GNU General Public License for more details.
12#
13# You should have received a copy of the GNU General Public License
14# along with this program. If not, see <http://www.gnu.org/licenses/>.
15
16# Test that removing a single-step breakpoint that is placed at the
17# same address as another regular breakpoint leaves the regular
18# breakpoint inserted.
19
20standard_testfile
21set executable ${testfile}
22
23if {[prepare_for_testing "failed to prepare" $testfile $srcfile debug]} {
24 return -1
25}
26
27if ![runto_main] then {
28 fail "Can't run to main"
29 return 0
30}
31
32gdb_breakpoint [gdb_get_line_number "set foo break here"]
33gdb_continue_to_breakpoint "first breakpoint" ".* set foo break here .*"
34
35gdb_breakpoint [gdb_get_line_number "set bar break here"]
36
37# So that GDB doesn't try to remove the regular breakpoint when the
38# step finishes.
39gdb_test_no_output "set breakpoint always-inserted on"
40
41# On software single-step targets, this step will want to momentarily
42# place a single-step breakpoint over the bar breakpoint, and then
43# remove it. But, a regular breakpoint is planted there already, and
44# with always-inserted on, should remain planted when the step
45# finishes.
46gdb_test "si" "Breakpoint .* bar break .*"
47
48# If the breakpoint is still correctly inserted, then this jump should
49# re-trigger it. Otherwise, GDB will lose control and the program
50# will exit.
51setup_kfail "breakpoints/17000" "*-*-*"
52gdb_test "jump *\$pc" "Breakpoint .* bar break .*"