From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [pushed] gdb/testsuite: accept variable number of spaces in gdb.base/jit-reader-simple.exp regex
Date: Mon, 2 Oct 2023 14:25:25 -0400 [thread overview]
Message-ID: <20231002182526.163668-1-simon.marchi@efficios.com> (raw)
I see this failure:
FAIL: gdb.base/jit-reader-simple.exp: standalone: change addr: initial run: maint info breakpoints shows jit breakpoint
The jit breakpoint expected by the test is there, it's just that the
number of spaces doesn't match what the test expects, after "jit
events":
-2 jit events keep y 0x0000555555555119 <__jit_debug_register_code> inf 1
Fix that by relaxing the regex a bit.
Change-Id: Ia3b04e6d5978399d940fd1a590f95f15275ca7ac
---
gdb/testsuite/gdb.base/jit-reader-simple.exp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.base/jit-reader-simple.exp b/gdb/testsuite/gdb.base/jit-reader-simple.exp
index dff195648753..8edce13ad97b 100644
--- a/gdb/testsuite/gdb.base/jit-reader-simple.exp
+++ b/gdb/testsuite/gdb.base/jit-reader-simple.exp
@@ -114,7 +114,7 @@ proc jit_test_reread {standalone change_addr} {
"get address of __jit_debug_descriptor"]
gdb_test "maint info breakpoints" \
- "jit events keep y $hex <__jit_debug_register_code>.*" \
+ "jit events\[ \]+keep y $hex <__jit_debug_register_code>.*" \
"maint info breakpoints shows jit breakpoint"
}
@@ -149,7 +149,7 @@ proc jit_test_reread {standalone change_addr} {
# This used to crash in the JIT-in-shared-library case:
# https://sourceware.org/bugzilla/show_bug.cgi?id=11094
gdb_test "maint info breakpoints" \
- "jit events keep y $hex <__jit_debug_register_code>.*" \
+ "jit events\[ \]+keep y $hex <__jit_debug_register_code>.*" \
"maint info breakpoints shows jit breakpoint"
}
base-commit: 4afdefc3375c81dd4780508b11bb2ade895d4053
--
2.42.0
reply other threads:[~2023-10-02 18:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231002182526.163668-1-simon.marchi@efficios.com \
--to=simon.marchi@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).