From: Yuriy Kolerov <kolerov93@gmail.com>
To: gdb-patches@sourceware.org, shahab@synopsys.com
Cc: Yuriy Kolerov <kolerov93@gmail.com>
Subject: [PATCH] arc: Don't build arc-analyze-prologue.S with -g
Date: Thu, 22 Feb 2024 08:02:19 +0000 [thread overview]
Message-ID: <20240222080219.51830-1-kolerov93@gmail.com> (raw)
arc-analyze-prologue.S test does not contain debug information thus
it must be compiled without -g option. Otherwise GDB will try to
unwind frames using debug information (which does not exist for .S
code!) instead of analyzing frames manually.
Signed-off-by: Yuriy Kolerov <kolerov93@gmail.com>
---
gdb/testsuite/gdb.arch/arc-analyze-prologue.exp | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/gdb/testsuite/gdb.arch/arc-analyze-prologue.exp b/gdb/testsuite/gdb.arch/arc-analyze-prologue.exp
index f414d9ccde0..371858ec0bc 100644
--- a/gdb/testsuite/gdb.arch/arc-analyze-prologue.exp
+++ b/gdb/testsuite/gdb.arch/arc-analyze-prologue.exp
@@ -19,7 +19,13 @@ require {istarget "arc*-*-*"}
standard_testfile .S
-if { [prepare_for_testing "failed to prepare" $testfile $srcfile] } {
+# arc-analyze-prologue.S test does not contain debug information thus it must
+# be compiled without -g option. Otherwise GDB will try to unwind frames using
+# debug information (which does not exist for .S code!) instead of analyzing
+# frames manually.
+set options {}
+
+if { [prepare_for_testing "failed to prepare" $testfile $srcfile $options] } {
return -1
}
--
2.39.2
next reply other threads:[~2024-02-22 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 8:02 Yuriy Kolerov [this message]
2024-02-27 14:03 ` Shahab Vahedi
2024-02-27 14:12 ` [PUSHED] " Shahab Vahedi
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=20240222080219.51830-1-kolerov93@gmail.com \
--to=kolerov93@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=shahab@synopsys.com \
/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).