From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH,v2] [testsuite] Fix timeout with maint print objfiles
Date: Tue, 27 Apr 2021 20:43:34 -0300 [thread overview]
Message-ID: <03b17c7c-bba6-87ab-6f3b-7fe938b3a382@linaro.org> (raw)
In-Reply-To: <9c009fdb-7464-7772-3320-52deaacfd69d@polymtl.ca>
On 4/27/21 3:45 PM, Simon Marchi wrote:
>
>
> On 2021-04-27 2:26 p.m., Luis Machado wrote:
>> Updates on v2:
>>
>> - Add missing exp_continue when looking for "readnow".
>> - Removed wraps
>>
>> --
>>
>> I'm seeing timeouts from gdb.rust/traits.exp when we attempt to print
>> things with "maint print objfiles".
>>
>> This happens for two reasons:
>>
>> 1 - GDB does not explicitly split each entry into its own line, but rather
>> relies on the terminal's width to insert line breaks.
>>
>> 2 - When running the GDB testsuite, such width may be unlimited, which will
>> prevent GDB from inserting any line breaks.
>>
>> As a result, the output may be too lengthy and will come in big lines. Tweak
>> the support library to match the patterns line-by-line, which gives us more
>> time to match things. Also fix GDB's output to print one entry per line,
>> regardless of the terminal width.
>>
>> A similar approach was used in another testcase using the same command (commit
>> eaeaf44cfdc9a4096a0dd52fa0606f29d4bfd48e). With the new line breaks, we don't
>> need a particular pattern, so clean up that test as well.
>>
>> gdb/ChangeLog:
>>
>> YYYY-MM-DD Luis Machado <luis.machado@linaro.org>
>>
>> * psymtab.c (psymbol_functions::dump): Output newline. Remove wrap.
>> * symmisc.c (dump_objfile): Likewise.
>>
>> gdb/testsuite/ChangeLog:
>>
>> YYYY-MM-DD Luis Machado <luis.machado@linaro.org>
>>
>> * gdb.base/maint.exp: Drop a pattern that is not needed.
>> * lib/gdb.exp (readnow): Match line-by-line.
>
> Thanks, that LGTM.
>
> Simon
>
Thanks! Pushed now.
prev parent reply other threads:[~2021-04-27 23:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 14:10 [PATCH] " Luis Machado via Gdb-patches
2021-04-27 15:47 ` Simon Marchi via Gdb-patches
2021-04-27 17:51 ` Luis Machado via Gdb-patches
2021-04-27 17:59 ` Simon Marchi via Gdb-patches
2021-04-27 18:26 ` [PATCH,v2] " Luis Machado via Gdb-patches
2021-04-27 18:45 ` Simon Marchi via Gdb-patches
2021-04-27 23:43 ` Luis Machado via Gdb-patches [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=03b17c7c-bba6-87ab-6f3b-7fe938b3a382@linaro.org \
--to=gdb-patches@sourceware.org \
--cc=luis.machado@linaro.org \
--cc=simon.marchi@polymtl.ca \
/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