From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH] [gdb/testsuite] Fix two test-cases on ppc64-linux
Date: Thu, 6 Aug 2026 10:28:17 +0200 [thread overview]
Message-ID: <20260806082817.2923965-1-tdevries@suse.de> (raw)
Fix two test-cases on ppc64-linux, where the .dot prefix used in the v1 ABI
is causing a mismatch.
Tested on ppc64-linux and x86_64-linux.
---
gdb/testsuite/gdb.ada/bp_c_mixed_case.exp | 6 +++++-
gdb/testsuite/gdb.opt/break-on-_exit.exp | 4 +++-
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.ada/bp_c_mixed_case.exp b/gdb/testsuite/gdb.ada/bp_c_mixed_case.exp
index 4dd4106649a..d428825e051 100644
--- a/gdb/testsuite/gdb.ada/bp_c_mixed_case.exp
+++ b/gdb/testsuite/gdb.ada/bp_c_mixed_case.exp
@@ -60,8 +60,12 @@ gdb_test "p <MixedCaseFunc>" \
" = void" \
"p <MixedCaseFunc>, in Ada"
+# The optional leading dot is for ppc64 v1 ABI function descriptors.
gdb_test "p <NoDebugMixedCaseFunc>" \
- " = {<text variable, no debug info>} $hex <NoDebugMixedCaseFunc>" \
+ [quotemeta \
+ [string cat \
+ {$@DECIMAL = {<text variable, no debug info>} @HEX} \
+ { <@/[.]?/NoDebugMixedCaseFunc>}]] \
"p <NoDebugMixedCaseFunc>, in Ada"
# Try inserting a breakpoint inside a C function. Because the function's
diff --git a/gdb/testsuite/gdb.opt/break-on-_exit.exp b/gdb/testsuite/gdb.opt/break-on-_exit.exp
index fa7cd96d61d..9caa54e4ad8 100644
--- a/gdb/testsuite/gdb.opt/break-on-_exit.exp
+++ b/gdb/testsuite/gdb.opt/break-on-_exit.exp
@@ -62,4 +62,6 @@ gdb_test "info shared"
# If the skip_prologue analysis of _exit is too eager, we may not hit the
# breakpoint.
-gdb_continue_to_breakpoint "_exit" "_exit \\(\\) .*"
+# The optional leading dot is for ppc64 v1 ABI function descriptors.
+gdb_continue_to_breakpoint "_exit" \
+ [quotemeta {@/[.]?/_exit () @...}]
base-commit: f94273aeb37908c32aa26530ff56e862f0060daf
--
2.51.0
next reply other threads:[~2026-08-06 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 8:28 Tom de Vries [this message]
2026-08-19 8:48 ` 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=20260806082817.2923965-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