public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Richard Bunt <richard.bunt@linaro.org>
To: tdevries@suse.de, tom@tromey.com
Cc: gdb-patches@sourceware.org, Richard Bunt <richard.bunt@linaro.org>
Subject: [PATCH v4] gdb: Enable early init of thread pool size
Date: Tue,  5 Dec 2023 13:10:41 +0000	[thread overview]
Message-ID: <20231205131041.1927330-1-richard.bunt@linaro.org> (raw)
In-Reply-To: <d88ff81e-b555-4246-908e-d6e30f309fb3@suse.de>

Sorry about this. Fix OK for trunk?

Commit 33ae45434d0 updated the text reported by GDB when showing the
number of work threads. However, it neglected to update the assertions
using this text, which caused index-file.exp to fail. This commit
corrects this omission.

Tested index-file.exp is fixed on my local machine.

---
 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 d0990dcfe0e..7e478ab9b60 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -10031,7 +10031,7 @@ proc is_target_non_stop { {testname ""} } {
 proc gdb_get_worker_threads { {testname ""} } {
     set worker_threads "UNKNOWN"
     gdb_test_multiple "maintenance show worker-threads" $testname {
-	-wrap -re "^The number of worker threads GDB can use is unlimited \\(currently ($::decimal)\\)\\." {
+	-wrap -re "^The number of worker threads GDB can use is the default \\(currently ($::decimal)\\)\\." {
 	    set worker_threads $expect_out(1,string)
 	}
 	-wrap -re "^The number of worker threads GDB can use is ($::decimal)\\." {
-- 
2.32.0


  parent reply	other threads:[~2023-12-05 13:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 16:13 Richard Bunt
2023-11-24 16:13 ` [PATCH v4 1/2] gdb: install CLI uiout while processing early init files Richard Bunt
2023-11-24 16:13 ` [PATCH v4 2/2] gdb: Enable early init of thread pool size Richard Bunt
2023-12-06 11:26   ` [PUSHED] gdb: fix libstdc++ assert caused by invalid use of std::clamp Andrew Burgess
2023-11-27 20:23 ` [PATCH v4] gdb: Enable early init of thread pool size Tom Tromey
2023-12-05  7:56   ` Tom de Vries
2023-12-05  9:35     ` Richard Bunt
2023-12-05 13:10     ` Richard Bunt [this message]
2023-12-05 14:39       ` Tom Tromey

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=20231205131041.1927330-1-richard.bunt@linaro.org \
    --to=richard.bunt@linaro.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.com \
    /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).