From: Tom Tromey <tom@tromey.com>
To: Richard Bunt <richard.bunt@linaro.org>
Cc: tdevries@suse.de, tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v4] gdb: Enable early init of thread pool size
Date: Tue, 05 Dec 2023 07:39:04 -0700 [thread overview]
Message-ID: <87cyvklnnb.fsf@tromey.com> (raw)
In-Reply-To: <20231205131041.1927330-1-richard.bunt@linaro.org> (Richard Bunt's message of "Tue, 5 Dec 2023 13:10:41 +0000")
>>>>> "Richard" == Richard Bunt <richard.bunt@linaro.org> writes:
Richard> Sorry about this. Fix OK for trunk?
Richard> Commit 33ae45434d0 updated the text reported by GDB when showing the
Richard> number of work threads. However, it neglected to update the assertions
Richard> using this text, which caused index-file.exp to fail. This commit
Richard> corrects this omission.
Richard> Tested index-file.exp is fixed on my local machine.
Looks good. Thank you.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2023-12-05 14:39 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
2023-12-05 14:39 ` Tom Tromey [this message]
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=87cyvklnnb.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=richard.bunt@linaro.org \
--cc=tdevries@suse.de \
/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).