[Bug libstdc++/104852] std::[j]thread::detach() still gives segmentation faults with glibc 2.34

2023-03-03 Thread aoliva at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104852 Alexandre Oliva changed: What|Removed |Added CC||aoliva at gcc dot gnu.org

[Bug libstdc++/104852] std::[j]thread::detach() still gives segmentation faults with glibc 2.34

2023-03-03 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104852 --- Comment #8 from CVS Commits --- The master branch has been updated by Alexandre Oliva : https://gcc.gnu.org/g:21edd841611a97442a6b95e8ec7e91ff8fd3a451 commit r13-6461-g21edd841611a97442a6b95e8ec7e91ff8fd3a451 Author: Alexandre Oliva

[Bug libstdc++/104852] std::[j]thread::detach() still gives segmentation faults with glibc 2.34

2022-03-09 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104852 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2022-03-09

[Bug libstdc++/104852] std::[j]thread::detach() still gives segmentation faults with glibc 2.34

2022-03-09 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104852 --- Comment #6 from Jonathan Wakely --- (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.

[Bug libstdc++/104852] std::[j]thread::detach() still gives segmentation faults with glibc 2.34

2022-03-09 Thread lightningdzeyenr at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104852 --- Comment #5 from Jackson Huff --- Just for reference, another person in bug 52590 had tried the same before but also had no luck.

[Bug libstdc++/104852] std::[j]thread::detach() still gives segmentation faults with glibc 2.34

2022-03-09 Thread lightningdzeyenr at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104852 --- Comment #4 from Jackson Huff --- (In reply to Jonathan Wakely from comment #2) > For distros other than Red Hat (and Fedora, CentOS etc.) you need to use: > > -Wl,--whole-archive -lpthread -Wl,--no-whole-archive > > Otherwise the pthread

[Bug libstdc++/104852] std::[j]thread::detach() still gives segmentation faults with glibc 2.34

2022-03-09 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104852 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/104852] std::[j]thread::detach() still gives segmentation faults with glibc 2.34

2022-03-09 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104852 --- Comment #2 from Jonathan Wakely --- This is the usual problem with weak symbols and static linking. For distros other than Red Hat (and Fedora, CentOS etc.) you need to use: -Wl,--whole-archive -lpthread -Wl,--no-whole-archive Otherwise

[Bug libstdc++/104852] std::[j]thread::detach() still gives segmentation faults with glibc 2.34

2022-03-08 Thread lightningdzeyenr at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104852 --- Comment #1 from Jackson Huff --- Note that my CMake command includes -lpthread even though CMake has been configured to link it already with -pthread, so when reproducing it, remove -lpthread to better replicate the situation (I only