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: improve test regexp in gdb_get_worker_threads
Date: Tue, 28 Nov 2023 18:21:21 +0000 (GMT)	[thread overview]
Message-ID: <20231128182121.2416B385AC25@sourceware.org> (raw)

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

commit b489eb90880aadadcbacfa2d9ed129732eebd834
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Tue Nov 28 18:17:23 2023 +0000

    gdb/testsuite: improve test regexp in gdb_get_worker_threads
    
    I spotted I made a small mistake in this commit:
    
      commit aff250145af6c7a8ea9332bc1306c1219f4a63db
      Date:   Fri Nov 24 12:04:36 2023 +0000
    
          gdb: generate gdb-index identically regardless of work thread count
    
    In this commit I added a new proc in testsuite/lib/gdb.exp called
    gdb_get_worker_threads.  This proc uses gdb_test_multiple with two
    possible patterns.  One pattern is anchored with '^', while the other
    is missing the '^' which it could use.
    
    This commit adds the missing '^'.

Diff:
---
 gdb/testsuite/lib/gdb.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index b534a61d066..d0990dcfe0e 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -10034,7 +10034,7 @@ proc gdb_get_worker_threads { {testname ""} } {
 	-wrap -re "^The number of worker threads GDB can use is unlimited \\(currently ($::decimal)\\)\\." {
 	    set worker_threads $expect_out(1,string)
 	}
-	-wrap -re "The number of worker threads GDB can use is ($::decimal)\\." {
+	-wrap -re "^The number of worker threads GDB can use is ($::decimal)\\." {
 	    set worker_threads $expect_out(1,string)
 	}
     }

                 reply	other threads:[~2023-11-28 18:21 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=20231128182121.2416B385AC25@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).