public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb/testsuite: resolve a duplicate test name in a gdb.mi test
Date: Sun,  3 Apr 2022 15:41:15 +0000 (GMT)	[thread overview]
Message-ID: <20220403154115.935043858430@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9f793f7beda340d847de19d9343d18400a1e21a3

commit 9f793f7beda340d847de19d9343d18400a1e21a3
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Sun Apr 3 16:36:48 2022 +0100

    gdb/testsuite: resolve a duplicate test name in a gdb.mi test
    
    Solve two duplicate test names in the test script:
    
      gdb.mi/mi-catch-cpp-exceptions.exp
    
    by moving the call to restart_for_test inside the with_test_prefix
    block.  There should be no difference in what is tested after this
    commit.

Diff:
---
 gdb/testsuite/gdb.mi/mi-catch-cpp-exceptions.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.mi/mi-catch-cpp-exceptions.exp b/gdb/testsuite/gdb.mi/mi-catch-cpp-exceptions.exp
index a909bb9d300..d8d7a57a766 100644
--- a/gdb/testsuite/gdb.mi/mi-catch-cpp-exceptions.exp
+++ b/gdb/testsuite/gdb.mi/mi-catch-cpp-exceptions.exp
@@ -183,8 +183,8 @@ with_test_prefix "all with -t" {
 
 if { $libstdcxx_probe_tests_supported  == 1 } {
     # Check that the temporary switch works when used with a regexp.
-    restart_for_test
     with_test_prefix "all with -t and regexp" {
+	restart_for_test
 	setup_catchpoint "throw" "-t -r my_ex"
 	setup_catchpoint "rethrow" "-t -r _except"
 	setup_catchpoint "catch" "-t -r my_exception"


                 reply	other threads:[~2022-04-03 15:41 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=20220403154115.935043858430@sourceware.org \
    --to=aburgess@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: link
Be 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).