aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.mi/mi-syn-frame.exp
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2021-12-23 15:48:47 +0000
committerAndrew Burgess <aburgess@redhat.com>2021-12-23 15:52:18 +0000
commitb6846ba57b4c6a8b613deefdaba512598ea3d0d0 (patch)
treed505595afbcd41b9880b0faae984ebc7b0bba028 /gdb/testsuite/gdb.mi/mi-syn-frame.exp
parentb622494ee378fd0a490c934c509364b4c7735273 (diff)
downloadfsf-binutils-gdb-b6846ba57b4c6a8b613deefdaba512598ea3d0d0.zip
fsf-binutils-gdb-b6846ba57b4c6a8b613deefdaba512598ea3d0d0.tar.gz
fsf-binutils-gdb-b6846ba57b4c6a8b613deefdaba512598ea3d0d0.tar.bz2
gdb/testsuite: resolve some duplicate testnames in gdb.mi
Set of fixes to resolve some duplicate test names in the gdb.mi/ directory. There should be no real test changes after this set of fixes, they are all either: - Adding with_test_prefix type constructs to make test names unique, or - Changing the test name to be more descriptive, or better reflect the test being run.
Diffstat (limited to 'gdb/testsuite/gdb.mi/mi-syn-frame.exp')
-rw-r--r--gdb/testsuite/gdb.mi/mi-syn-frame.exp12
1 files changed, 7 insertions, 5 deletions
diff --git a/gdb/testsuite/gdb.mi/mi-syn-frame.exp b/gdb/testsuite/gdb.mi/mi-syn-frame.exp
index 21f506b..0d9a710 100644
--- a/gdb/testsuite/gdb.mi/mi-syn-frame.exp
+++ b/gdb/testsuite/gdb.mi/mi-syn-frame.exp
@@ -55,11 +55,12 @@ mi_gdb_test "402-stack-list-frames" "402\\^done,stack=\\\[frame=\{level=\"0\",ad
#
mi_send_resuming_command "exec-continue" "testing exec continue"
-mi_expect_stop "really-no-reason" "" "" "" "" "" "finished exec continue"
+mi_expect_stop "really-no-reason" "" "" "" "" "" \
+ "finished exec continue after calling foo"
mi_gdb_test "404-stack-list-frames 0 0" \
"404\\^done,stack=\\\[frame=\{level=\"0\",addr=\"$hex\",func=\"main\",file=\".*mi-syn-frame.c\",fullname=\"${fullname_syntax}${srcfile}\",line=\"$decimal\",arch=\"$any\"\}.*\\\]" \
- "list stack frames"
+ "list stack frames, back in main after calling foo"
#
@@ -79,16 +80,17 @@ mi_gdb_test "406-data-evaluate-expression have_a_very_merry_interrupt()" \
mi_gdb_test "407-stack-list-frames" \
"407\\^done,stack=\\\[frame=\{level=\"0\",addr=\"$hex\",func=\"subroutine\",file=\".*mi-syn-frame.c\",fullname=\"${fullname_syntax}${srcfile}\",line=\"$decimal\",arch=\"$any\"\},frame=\{level=\"1\",addr=\"$hex\",func=\"handler\",file=\".*mi-syn-frame.c\",fullname=\"${fullname_syntax}${srcfile}\",line=\"$decimal\",arch=\"$any\"\},frame=\{level=\"2\",addr=\"$hex\",func=\"<signal handler called>\"\},.*frame=\{level=\"$decimal\",addr=\"$hex\",func=\"have_a_very_merry_interrupt\",file=\".*mi-syn-frame.c\",fullname=\"${fullname_syntax}${srcfile}\",line=\"$decimal\",arch=\"$any\"\},frame=\{level=\"$decimal\",addr=\"$hex\",func=\"<function called from gdb>\"\},frame=\{level=\"$decimal\",addr=\"$hex\",func=\"main\",file=\".*mi-syn-frame.c\",fullname=\"${fullname_syntax}${srcfile}\",line=\"$decimal\",arch=\"$any\"\}.*\\\]" \
- "list stack frames"
+ "list stack frames, with signal handler and dummy frame"
mi_send_resuming_command "exec-continue" "testing exec continue"
-mi_expect_stop "really-no-reason" "" "" "" "" "" "finished exec continue"
+mi_expect_stop "really-no-reason" "" "" "" "" "" \
+ "finished exec continue after calling have_a_very_merry_interrupt"
mi_gdb_test "409-stack-list-frames 0 0" \
"409\\^done,stack=\\\[frame=\{level=\"0\",addr=\"$hex\",func=\"main\",file=\".*mi-syn-frame.c\",fullname=\"${fullname_syntax}${srcfile}\",line=\"$decimal\",arch=\"$any\"\}.*\\\]" \
- "list stack frames"
+ "list stack frames, back in main after calling have_a_very_merry_interrupt"
#
# Call bar() by hand, which should get an exception while running.