public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104852] std::[j]thread::detach() still gives segmentation faults with glibc 2.34
Date: Wed, 09 Mar 2022 18:55:10 +0000	[thread overview]
Message-ID: <bug-104852-4-SptJ5Nvq4A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104852-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104852

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jackson Huff from comment #5)
> Just for reference, another person in bug 52590 had tried the same before
> but also had no luck.

No, they tried a different command, not the one I suggested.

I just checked out the code in an Ubuntu container and running make VERBOSE=1 I
see that the flags are added to the start of the command:

[100%] Linking CXX executable hajime
/usr/bin/cmake -E cmake_link_script CMakeFiles/hajime.dir/link.txt --verbose=1
/usr/bin/c++  -static -Wl,--whole-archive -lpthread -Wl,--no-whole-archive -O3
-DNDEBUG -s -flto -fno-fat-lto-objects -flto=auto
CMakeFiles/hajime.dir/hajime.cpp.o CMakeFiles/hajime.dir/server.cpp.o
CMakeFiles/hajime.dir/server_features.cpp.o
CMakeFiles/hajime.dir/server_performance.cpp.o
CMakeFiles/hajime.dir/server_performance_counters.cpp.o
CMakeFiles/hajime.dir/getvarsfromfile.cpp.o CMakeFiles/hajime.dir/output.cpp.o
CMakeFiles/hajime.dir/installer.cpp.o CMakeFiles/hajime.dir/deduce.cpp.o
CMakeFiles/hajime.dir/languages.cpp.o CMakeFiles/hajime.dir/wizard.cpp.o
CMakeFiles/hajime.dir/constants.cpp.o -o hajime 

That is wrong:
https://web.archive.org/web/20210609020437/c-faq.com/lib/libsearch.html

  parent reply	other threads:[~2022-03-09 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09  4:13 [Bug libstdc++/104852] New: " lightningdzeyenr at gmail dot com
2022-03-09  4:16 ` [Bug libstdc++/104852] " lightningdzeyenr at gmail dot com
2022-03-09 17:36 ` redi at gcc dot gnu.org
2022-03-09 17:40 ` redi at gcc dot gnu.org
2022-03-09 17:42 ` lightningdzeyenr at gmail dot com
2022-03-09 17:46 ` lightningdzeyenr at gmail dot com
2022-03-09 18:55 ` redi at gcc dot gnu.org [this message]
2022-03-09 19:18 ` redi at gcc dot gnu.org
2023-03-03 19:10 ` cvs-commit at gcc dot gnu.org
2023-03-03 19:39 ` aoliva 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-104852-4-SptJ5Nvq4A@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).