public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/95989] Segmentation fault compiling with static libraries and using jthread::request_stop
Date: Wed, 01 Jul 2020 13:28:14 +0000 [thread overview]
Message-ID: <bug-95989-4-quZux18rPj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95989-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95989
Florian Weimer <fw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fw at gcc dot gnu.org
--- Comment #9 from Florian Weimer <fw at gcc dot gnu.org> ---
Jonathan and I discussed this off this bug.
The issue is the weak declaration of pthread_self in the libstdc++ headers.
For glibc (at least since 2.1, possibly 2.0), there is no reason to have a weak
declaration because the symbol lives in libc itself, so it is always available
(both with static and dynamic linking). But if the symbol reference is weak and
the symbol is not pulled in for some other reason, then the function is not
linked in even if it is called.
next prev parent reply other threads:[~2020-07-01 13:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 20:25 [Bug libstdc++/95989] New: " webrown.cpp at gmail dot com
2020-06-30 22:35 ` [Bug libstdc++/95989] " redi at gcc dot gnu.org
2020-06-30 22:59 ` antal.buss at ualberta dot ca
2020-06-30 23:21 ` redi at gcc dot gnu.org
2020-06-30 23:30 ` redi at gcc dot gnu.org
2020-06-30 23:39 ` redi at gcc dot gnu.org
2020-07-01 10:15 ` redi at gcc dot gnu.org
2020-07-01 13:28 ` fw at gcc dot gnu.org [this message]
2020-07-01 13:53 ` redi at gcc dot gnu.org
2020-07-06 12:38 ` fw at gcc dot gnu.org
2020-07-08 14:39 ` redi at gcc dot gnu.org
2020-07-08 15:36 ` redi at gcc dot gnu.org
2020-07-09 9:58 ` redi at gcc dot gnu.org
2020-11-11 17:26 ` redi at gcc dot gnu.org
2020-11-19 21:07 ` cvs-commit at gcc dot gnu.org
2020-11-20 13:49 ` cvs-commit at gcc dot gnu.org
2020-11-20 13:52 ` redi at gcc dot gnu.org
2021-09-21 13:42 ` ebotcazou at gcc dot gnu.org
2022-03-04 4:08 ` lightningdzeyenr at gmail dot com
2022-03-04 9:25 ` redi at gcc dot gnu.org
2022-03-09 4:27 ` lightningdzeyenr at gmail dot com
2023-03-03 19:10 ` cvs-commit at gcc dot gnu.org
2024-04-10 12:56 ` redi at gcc dot gnu.org
2024-04-10 17:32 ` pinskia 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-95989-4-quZux18rPj@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).