public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "webrown.cpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/95989] New: Segmentation fault compiling with static libraries and using jthread::request_stop Date: Tue, 30 Jun 2020 20:25:47 +0000 [thread overview] Message-ID: <bug-95989-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95989 Bug ID: 95989 Summary: Segmentation fault compiling with static libraries and using jthread::request_stop Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: antal.buss at ualberta dot ca CC: webrown.cpp at gmail dot com Target Milestone: --- CC: webrown.cpp at gmail dot com A simple program creating a jthread and later calling request_stop on the created thread produces a segmentation fault when the program is compiled against the static libraries but works fine using dynamic libraries. --- Comment #1 from Antal Buss <antal.buss at ualberta dot ca> --- Created attachment 48811 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48811&action=edit Preprocessed file --- Comment #2 from Antal Buss <antal.buss at ualberta dot ca> --- Created attachment 48812 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48812&action=edit Compiler output --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- *** Bug 95990 has been marked as a duplicate of this bug. *** --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- *** Bug 95991 has been marked as a duplicate of this bug. ***
next reply other threads:[~2020-06-30 20:25 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-30 20:25 webrown.cpp at gmail dot com [this message] 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 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@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: linkBe 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).