From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH] [gdb/testsuite] Fix gdb.tui/resize-3.exp on ppc64-linux
Date: Fri, 17 Oct 2025 15:39:57 +0200 [thread overview]
Message-ID: <20251017133957.2464782-1-tdevries@suse.de> (raw)
On ppc64-linux, with test-case gdb.tui/resize-3.exp I run into:
...
FAIL: gdb.tui/resize-3.exp: after resize: Assembler for foo is shown
...
because the disassembly window shows:
...
0 +----------------------------------------------------------------------+
1 | 0x10000093c <.foo> std r31,-8(r1) |
2 | 0x100000940 <.foo+4> stdu r1,-64(r1) |
3 | 0x100000944 <.foo+8> mr r31,r1 |
4 |B+>0x100000948 <.foo+12> li r9,0 |
...
and we grep for "<foo".
Fix this by updating the regexp.
Tested on ppc64-linux and x86_64-linux.
---
gdb/testsuite/gdb.tui/resize-3.exp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/testsuite/gdb.tui/resize-3.exp b/gdb/testsuite/gdb.tui/resize-3.exp
index fcda407c9fd..5a3d50aef48 100644
--- a/gdb/testsuite/gdb.tui/resize-3.exp
+++ b/gdb/testsuite/gdb.tui/resize-3.exp
@@ -69,5 +69,5 @@ with_test_prefix "after resize" {
"No Assembly message is not displayed" \
"No Assembly Available"
Term::check_contents "Assembler for foo is shown" \
- "$hex\\s+<foo"
+ [string cat $hex {\s+} "<" ([string_to_regexp .])? "foo"]
}
base-commit: 0e4fd060ee7244d00c76f0d4815063dfcc9877f1
--
2.51.0
next reply other threads:[~2025-10-17 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 13:39 Tom de Vries [this message]
2025-10-17 14:14 ` Tom Tromey
2025-10-18 8:21 ` Tom de Vries
2025-10-18 9:11 ` Tom de Vries
2025-10-18 17:19 ` Tom Tromey
2025-10-20 10:08 ` Tom de Vries
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=20251017133957.2464782-1-tdevries@suse.de \
--to=tdevries@suse.de \
--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