From: Tom de Vries <tdevries@suse.de>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PUSHED] gdb/testsuite: small fix for amd64-extended-prologue-analysis.exp
Date: Mon, 8 Sep 2025 15:48:11 +0200 [thread overview]
Message-ID: <f18c70e1-9880-4615-8c8b-61371a8813e1@suse.de> (raw)
In-Reply-To: <8735dae5139ecf2d3a79508371c9c861fde12c44.1757323506.git.aburgess@redhat.com>
On 9/8/25 11:25, Andrew Burgess wrote:
> I noticed I was sometimes getting this failure:
>
> FAIL: gdb.arch/amd64-extended-prologue-analysis.exp: offset \
> initialization: ASM source: gdb_breakpoint: set breakpoint \
> at *0x0000000000401151
>
> The problem was introduced in commit:
>
> commit f9aa48dc545ef511e19f4dfab88a196b820fd2da
> Date: Thu Aug 28 11:50:13 2025 +0000
>
> gdb, amd64: extend the amd64 prologue analyzer to skip register pushes
>
> A gdb_test_multiple exits early when processing the results of a
> 'disassemble' command, without waiting for the prompt to be seen.
> This can leave unhandled output in expect's input buffer, which will
> then throw off the next test.
>
> Update the gdb_test_multiple to wait for the prompt before declaring
> the test passed.
>
> After this I'm no longer seeing the above failure.
>
Hi Andrew,
thanks for fixing this.
I've managed to reproduce the problem reliably using check-read1, and
verified that the patch fixes it.
Thanks,
- Tom
> There should be no change in what is tested after this commit.
> ---
> .../gdb.arch/amd64-extended-prologue-analysis.exp | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.arch/amd64-extended-prologue-analysis.exp b/gdb/testsuite/gdb.arch/amd64-extended-prologue-analysis.exp
> index b2fcbe66034..356afc7e668 100644
> --- a/gdb/testsuite/gdb.arch/amd64-extended-prologue-analysis.exp
> +++ b/gdb/testsuite/gdb.arch/amd64-extended-prologue-analysis.exp
> @@ -59,9 +59,13 @@ proc offset_test_run {} {
>
> set addr_past_prologue "null"
> gdb_test_multiple "disassemble" "Disassemble foo" -lbl {
> - -re "($::hex) <\\+($::decimal)>:\\s*mov.*" {
> + -re "\r\n\\s*($::hex) <\\+($::decimal)>:\\s*mov.*(?=\r\n)" {
> set addr_past_prologue $expect_out(1,string)
> - pass $gdb_test_name
> + exp_continue
> + }
> +
> + -re -wrap "" {
> + gdb_assert { $addr_past_prologue ne "null" } $gdb_test_name
> }
> }
>
>
> base-commit: 5d0ac9ee8fd007e90ba3fef3b95fd756cc191401
prev parent reply other threads:[~2025-09-08 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 9:25 Andrew Burgess
2025-09-08 9:31 ` Andrew Burgess
2025-09-08 13:48 ` Tom de Vries [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=f18c70e1-9880-4615-8c8b-61371a8813e1@suse.de \
--to=tdevries@suse.de \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.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