public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/111315] libstdc++ stacktrace testsuite failures with --enable-default-pie
Date: Thu, 07 Sep 2023 10:34:51 +0000 [thread overview]
Message-ID: <bug-111315-4-UZG7CYEBjp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111315-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111315
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xry111 at gcc dot gnu.org
--- Comment #2 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Rimvydas (RJ) from comment #0)
> The GCC configured with --enable-default-pie gives:
>
> === libstdc++ tests ===
>
> Running target unix
> FAIL: 19_diagnostics/stacktrace/entry.cc execution test
> FAIL: 19_diagnostics/stacktrace/stacktrace.cc execution test
>
> libstdc++-v3/testsuite/19_diagnostics/stacktrace/entry.cc:39: void
> test_members(): Assertion 'e1.source_line() == (__LINE__ - 5)' failed.
> libstdc++-v3/testsuite/19_diagnostics/stacktrace/stacktrace.cc:132: void
> test_assign(): Assertion 's0.at(0).source_line() == (__LINE__ - 4)' failed.
>
> In both cases source_line() methods return 0.
>
> Also, the -fno-pie option cannot be used when linking these tescases:
> /usr/bin/ld: /tmp/ccv2BTff.o: relocation R_X86_64_32 against symbol
> `_ZNSt16stacktrace_entry14_S_err_handlerEPvPKci' can not be used when making
> a PIE object; recompile with -fPIE
You need to use both -no-pie and -fno-pie. -fno-pie only tells the compiler
not to emit code for PIE, -no-pie tells the linker not to link the code for
PIE.
next prev parent reply other threads:[~2023-09-07 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 3:49 [Bug libstdc++/111315] New: " rimvydas.jas at gmail dot com
2023-09-07 3:58 ` [Bug libstdc++/111315] " pinskia at gcc dot gnu.org
2023-09-07 10:34 ` xry111 at gcc dot gnu.org [this message]
2023-09-07 10:38 ` xry111 at gcc dot gnu.org
2023-10-31 20:06 ` [Bug libbacktrace/111315] " pinskia at gcc dot gnu.org
2023-11-03 10:03 ` xry111 at gcc dot gnu.org
2023-11-03 16:26 ` rimvydas.jas at gmail dot com
2023-11-03 16:32 ` redi at gcc dot gnu.org
2023-11-06 23:11 ` cvs-commit at gcc dot gnu.org
2023-11-06 23:12 ` cvs-commit at gcc dot gnu.org
2023-11-06 23:13 ` cvs-commit at gcc dot gnu.org
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-111315-4-UZG7CYEBjp@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).