espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-06-19 17:18:24 +08:00
Code Issues Packages Projects Releases Wiki Activity

gdb/testsuite: Remove duplicates from gdb.base/call-signal-resume.exp

Browse Source 
When running the testsuite, I have:

    Running .../gdb/testsuite/gdb.base/call-signal-resume.exp ...
    DUPLICATE: gdb.base/call-signal-resume.exp: dummy stack frame number
    DUPLICATE: gdb.base/call-signal-resume.exp: set confirm off
    DUPLICATE: gdb.base/call-signal-resume.exp: return

This is due to the fact that a pattern was probably copy/pasted to
re-use the logic while not adjusting the test names to avoid the
duplication.

Fix by removing the redundant tests ('set confirm off' only needs to be
used once) and adjusting the test names where appropriate.

Tested on x86_64-linux.
This commit is contained in:
Lancelot SIX
2021-11-21 15:22:49 +00:00
parent 148ac50e89
commit 8cc261b781
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
gdb/testsuite/gdb.base/call-signal-resume.exp
View File

@ -116,18 +116,17 @@ gdb_test "call null_hand_call ()" "Breakpoint \[0-9\]*, null_hand_call.*" \
set frame_number [get_dummy_frame_number]
if { "$frame_number" == "" } {
fail "dummy stack frame number"
fail "dummy stack frame number, two"
setup_xfail "*-*-*"
# Need something.
set frame_number 0
} else {
pass "dummy stack frame number"
pass "dummy stack frame number, two"
}
# Pop the dummy frame.
gdb_test "frame $frame_number" ".*"
gdb_test_no_output "set confirm off"
gdb_test "return" ""
gdb_test "return" "" "return, two"
# Continue again, this time we should get to the signal handler.