diff options
| author | Lancelot SIX <lsix@lancelotsix.com> | 2021-11-21 15:22:49 +0000 |
|---|---|---|
| committer | Lancelot SIX <lsix@lancelotsix.com> | 2022-01-07 22:43:34 +0000 |
| commit | 8cc261b7814cdd04735be2e7af1fafc19df1b3b6 (patch) | |
| tree | 2c3f9aace9c1240195cb28456521086bdf51d715 | |
| parent | 148ac50e89b66c1d7934f464195ba559f5cc8cd0 (diff) | |
| download | binutils-8cc261b7814cdd04735be2e7af1fafc19df1b3b6.zip binutils-8cc261b7814cdd04735be2e7af1fafc19df1b3b6.tar.gz binutils-8cc261b7814cdd04735be2e7af1fafc19df1b3b6.tar.bz2 | |
gdb/testsuite: Remove duplicates from gdb.base/call-signal-resume.exp
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.
| -rw-r--r-- | gdb/testsuite/gdb.base/call-signal-resume.exp | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/gdb/testsuite/gdb.base/call-signal-resume.exp b/gdb/testsuite/gdb.base/call-signal-resume.exp index 011ca85..5b3f105 100644 --- a/gdb/testsuite/gdb.base/call-signal-resume.exp +++ b/gdb/testsuite/gdb.base/call-signal-resume.exp @@ -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. |