blob: 27c2a77f2104eee4e37346f7418894ae9c4cb7d0 [file] [log] [blame]
# Copyright 2008-2021 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
# 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 <>.
# This file is part of the GDB testsuite.
# 'reverse-finish' used to have a bug where user breakpoints set at
# the functions entry would be ignored. Make sure the bug doesn't
# reappear.
if ![supports_reverse] {
standard_testfile finish-reverse.c
if { [prepare_for_testing "failed to prepare" "$testfile" $srcfile] } {
return -1
if ![runto_main] then {
return 0
if [supports_process_record] {
# Activate process record/replay
gdb_test_no_output "record" "turn on process record"
set breakloc [gdb_get_line_number "VOID FUNC" "$srcfile"]
gdb_test "tbreak void_func" \
"Temporary breakpoint $decimal at .*$srcfile, line $breakloc\." \
"set breakpoint on void_func"
gdb_continue_to_breakpoint "void_func" ".*$srcfile:$breakloc.*"
# We stop at the brekapoint on void_func, but breakpoint on
# *void_func will be set at the same place if function void_func doesn't
# have prologue. One step forward to avoid this.
gdb_test "si"
gdb_test "break \*void_func" \
"Breakpoint $decimal at .*" \
"set breakpoint at void_func's entry"
gdb_test "reverse-finish" \
".*Breakpoint .*, void_func.*" \
"reverse-finish from void_func trips breakpoint at entry"
gdb_test "frame" "#0 void_func.*" "no spurious proceed after breakpoint stop"