public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/31564] New: [gdb/testsuite, unix/-fPIE/-pie] FAIL: gdb.base/rtld-step.exp: runto: run to main
Date: Wed, 27 Mar 2024 05:25:58 +0000 [thread overview]
Message-ID: <bug-31564-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31564
Bug ID: 31564
Summary: [gdb/testsuite, unix/-fPIE/-pie] FAIL:
gdb.base/rtld-step.exp: runto: run to main
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On aarch64-linux, with target board unix/-fPIE/-pie, I run into:
...
(gdb) run ^M
Starting program:
/home/vries/gdb/build/gdb/testsuite/outputs/gdb.base/rtld-step/rtld-step-main
^M
During startup program terminated with signal SIGSEGV, Segmentation fault.^M
(gdb) FAIL: gdb.base/rtld-step.exp: runto: run to main
...
The test-case tries to generate static PIE, so there's probably a conflict in
compile options.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2024-03-27 5: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=bug-31564-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).