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/29244] [gdb/testsuite, gcc 4.8] Problems with -static and target board unix/-fPIE/-pie
Date: Mon, 05 Jun 2023 14:14:26 +0000 [thread overview]
Message-ID: <bug-29244-4717-19oIxNWhXz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29244-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29244
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Likewise, with aarch64-linux I run into:
...
FAIL: gdb.base/break-entry.exp: running to .* in runto
FAIL: gdb.base/catch-fork-static.exp: run to fork
FAIL: gdb.threads/staticthreads.exp: continue to main's call of sem_post
FAIL: gdb.threads/staticthreads.exp: handle SIG32 helps
FAIL: gdb.threads/staticthreads.exp: running to main in runto
FAIL: gdb.threads/staticthreads.exp: running to main in runto
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step back into _start
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step back into foo
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step into bar
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step into foo
...
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-06-05 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 10:25 [Bug testsuite/29244] New: " vries at gcc dot gnu.org
2022-06-11 10:31 ` [Bug testsuite/29244] " vries at gcc dot gnu.org
2023-06-05 14:14 ` vries at gcc dot gnu.org [this message]
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-29244-4717-19oIxNWhXz@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).