public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou 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: Tue, 21 Sep 2021 13:42:14 +0000 [thread overview] Message-ID: <bug-95989-4-6uYJBYGYjy@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 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ebotcazou at gcc dot gnu.org --- Comment #19 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- The test fails on a SPARC64/Linux box with: GNU C Library (Debian GLIBC 2.32-4) stable release version 2.32. Copyright (C) 2020 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled by GNU CC version 10.3.0. libc ABIs: UNIQUE IFUNC ABSOLUTE For bug reporting instructions, please see: <http://www.debian.org/Bugs/>. It looks like we have the same problem with pthread_join now: Thread 1 "95989" received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () #1 0x0000000000105670 in __gthread_join ( __value_ptr=<error reading variable: dwarf2_find_location_expression: Corrupted DWARF expression.>, __threadid=<error reading variable: dwarf2_find_location_expression: Corrupted DWARF expression.>) at /home/ebotcazou/build/sparc64-linux-gnu/libstdc++-v3/include/sparc64-linux-gnu/bits/gthr-default.h:669 #2 std::thread::join (this=0x7fefffff0b0) at /home/ebotcazou/src/libstdc++-v3/src/c++11/thread.cc:112 #3 0x0000000000103164 in std::jthread::join (this=0x7fefffff0a8) at /home/ebotcazou/install/include/c++/12.0.0/thread:160 #4 0x00000000001030e8 in std::jthread::~jthread (this=0x7fefffff0a8, __in_chrg=<optimized out>) at /home/ebotcazou/install/include/c++/12.0.0/thread:130 #5 0x0000000000100d88 in test01 () at 95989.cc:33 #6 0x0000000000100ea8 in main () at 95989.cc:52
next prev parent reply other threads:[~2021-09-21 13:42 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 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 [this message] 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-6uYJBYGYjy@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).