From: Simon Marchi <simark@simark.ca>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb.gdb/python-helper.exp: Increase timeout values
Date: Sun, 6 Sep 2026 14:52:40 -0400 [thread overview]
Message-ID: <a3de7b86-25e7-4382-b198-db3c4d1cc8fa@simark.ca> (raw)
In-Reply-To: <20260906040140.158197-1-thiago.bauermann@linaro.org>
On 2026-09-06 00:01, Thiago Jung Bauermann wrote:
> In the three Linux machines I tested (my x86_64 laptop and two aarch64
> servers), gdb.gdb/python-helper.exp has this timeout failure:
>
> FAIL: gdb.gdb/python-helper.exp: pretty print type instance flags (timeout)
>
> And the slower aarch64 server also has this one:
>
> FAIL: gdb.gdb/python-helper.exp: start inner gdb (timeout)
>
> Fix these failures by using timeout factors. For the latter, a 2x factor
> is enough. For the former, I needed 8x. It appears that the "pretty print
> type instance flags" test is quite demanding.
Out of curiosity, is this with GDB build at -O0 or -O2 (or something
else)? With ASan or other instrumentation?
I am asking because if it's -O2, then it's representative of what a user
would have in their hands. If some commands take a minute to run, then
we could at least check if it's because GDB is doing something terribly
inefficient.
Simon
prev parent reply other threads:[~2026-09-06 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 4:01 Thiago Jung Bauermann
2026-09-06 15:58 ` Tom de Vries
2026-09-06 20:13 ` Thiago Jung Bauermann
2026-09-07 1:02 ` Simon Marchi
2026-09-07 4:21 ` Thiago Jung Bauermann
2026-09-06 18:52 ` Simon Marchi [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=a3de7b86-25e7-4382-b198-db3c4d1cc8fa@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.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