mirror of
https://github.com/espressif/binutils-gdb.git
synced 2025-06-19 09:14:14 +08:00
gdb/testsuite: Remove duplicates from gdb.mi/mi-nonstop.exp
When running the testsuite, I have: Running .../gdb/testsuite/gdb.mi/mi-nonstop.exp ... DUPLICATE: gdb.mi/mi-nonstop.exp: check varobj, w1, 1 DUPLICATE: gdb.mi/mi-nonstop.exp: stacktrace of stopped thread Fix by adjusting the problematic test names. Tested on x86_64-linux.
This commit is contained in:
@ -112,7 +112,7 @@ mi_check_thread_states {"running" "running" "stopped"} "thread state, stop on co
|
||||
# Check that when we update all varobj, we don't get no error about varobj
|
||||
# bound to running thread.
|
||||
mi_varobj_update * {I_W1} "update varobj, 2"
|
||||
mi_check_varobj_value I_W1 3 "check varobj, w1, 1"
|
||||
mi_check_varobj_value I_W1 3 "check varobj, w1, 2"
|
||||
|
||||
|
||||
# Check that stack commands are allowed on a stopped thread, even if some other threads
|
||||
@ -147,6 +147,6 @@ if { [mi_is_target_remote] } {
|
||||
# See that we can still poke other threads.
|
||||
mi_gdb_test "-stack-list-frames --thread 3" \
|
||||
"\\^done,stack=\\\[frame={level=\"0\",addr=\".*\",func=\"break_at_me\".*" \
|
||||
"stacktrace of stopped thread"
|
||||
"stacktrace of stopped thread, 2"
|
||||
|
||||
mi_gdb_exit
|
||||
|
Reference in New Issue
Block a user