public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Lancelot SIX <lsix@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb/testsuite: Remove duplicates from gdb.mi/mi-nonstop.exp Date: Fri, 7 Jan 2022 22:46:57 +0000 (GMT) [thread overview] Message-ID: <20220107224657.B85C93858421@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=94e3acde23ca8e68e14817661740e692d3f3e738 commit 94e3acde23ca8e68e14817661740e692d3f3e738 Author: Lancelot SIX <lsix@lancelotsix.com> Date: Tue Nov 23 13:35:47 2021 +0000 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. Diff: --- gdb/testsuite/gdb.mi/mi-nonstop.exp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gdb/testsuite/gdb.mi/mi-nonstop.exp b/gdb/testsuite/gdb.mi/mi-nonstop.exp index 0ed6c2ef5f6..fe9392e314e 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
reply other threads:[~2022-01-07 22:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220107224657.B85C93858421@sourceware.org \ --to=lsix@sourceware.org \ --cc=gdb-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).