public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Richard Bunt <richard.bunt@linaro.org>
To: Tom de Vries <tdevries@suse.de>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4] gdb: Enable early init of thread pool size
Date: Tue, 5 Dec 2023 09:35:35 +0000	[thread overview]
Message-ID: <8ac74963-0268-49ab-a88c-e4bc943bea49@linaro.org> (raw)
In-Reply-To: <d88ff81e-b555-4246-908e-d6e30f309fb3@suse.de>



On 05/12/2023 07:56, Tom de Vries wrote:
> On 11/27/23 21:23, Tom Tromey wrote:
>>>>>>> "Richard" == Richard Bunt <richard.bunt@linaro.org> writes:
>>
>> Richard> Updates in v4.
>> Richard> Clamped the default number of worker threads to eight. I'm ok 
>> with this as GDB
>> Richard> can always be configured to use a higher number of work 
>> threads if the use case
>> Richard> demands it.
>>
>> I think these are fine.  Thank you for doing this.
>> Approved-By: Tom Tromey <tom@tromey.com>
> 
> I think this caused:
> ...
> FAIL: gdb.gdb/index-file.exp: maintenance show worker-threads
> ERROR: tcl error sourcing 
> /data/vries/gdb/src/gdb/testsuite/gdb.gdb/index-file.exp.
> ERROR: invalid bareword "UNKNOWN"
> in expression "UNKNOWN / 2";
> should be "$UNKNOWN" or "{UNKNOWN}" or "UNKNOWN(...)" or ...
>      (parsing expression "UNKNOWN / 2")
>      invoked from within
> "expr $worker_threads / 2"
>      invoked from within
> "if { $worker_threads > 1 } {
>      # Start GDB, but don't load a file yet.
>      clean_restart
> 
>      # Adjust the number of threads to use.
>      set reduced..."
>      (file "/data/vries/gdb/src/gdb/testsuite/gdb.gdb/index-file.exp" 
> line 127)
>      invoked from within
> "source /data/vries/gdb/src/gdb/testsuite/gdb.gdb/index-file.exp"
>      ("uplevel" body line 1)
>      invoked from within
> "uplevel #0 source 
> /data/vries/gdb/src/gdb/testsuite/gdb.gdb/index-file.exp"
>      invoked from within
> "catch "uplevel #0 source $test_file_name""
> ...
> 
> Thanks,
> - Tom

Thanks for flagging.

I'm looking in to the issue.

Rich.

  reply	other threads:[~2023-12-05  9:35 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 [this message]
2023-12-05 13:10     ` Richard Bunt
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=8ac74963-0268-49ab-a88c-e4bc943bea49@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).