diff options
| author | Lancelot SIX <lsix@lancelotsix.com> | 2021-11-23 13:35:47 +0000 |
|---|---|---|
| committer | Lancelot SIX <lsix@lancelotsix.com> | 2022-01-07 22:43:34 +0000 |
| commit | 94e3acde23ca8e68e14817661740e692d3f3e738 (patch) | |
| tree | 0e47d649afd55b7760a1fa9e77155bfbe728e43a | |
| parent | b4130189f92809afd76d1fd1f16aee8c4474cccd (diff) | |
| download | binutils-94e3acde23ca8e68e14817661740e692d3f3e738.zip binutils-94e3acde23ca8e68e14817661740e692d3f3e738.tar.gz binutils-94e3acde23ca8e68e14817661740e692d3f3e738.tar.bz2 | |
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.
| -rw-r--r-- | gdb/testsuite/gdb.mi/mi-nonstop.exp | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/testsuite/gdb.mi/mi-nonstop.exp b/gdb/testsuite/gdb.mi/mi-nonstop.exp index 0ed6c2e..fe9392e 100644 --- a/gdb/testsuite/gdb.mi/mi-nonstop.exp +++ b/gdb/testsuite/gdb.mi/mi-nonstop.exp @@ -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 |