SIGSEGV at _dl_runtime_resolve_xsavec in boost::detail::set_current_thread_data
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- operating-systems
Research direction
Start with the GDB backtrace at boost::detail::set_current_thread_data and thread_proxy, using Boost 1.84.0 and the failing boost::thread configuration. Try to reduce the report to a reproducible example and compare it with std::thread; done requires identifying a reproducible cause or a confirmed fix path.
Written by the indexing model from the issue text.
Description
I started running into this SIGSEGV. Is it possible that some thread-local variable initialization could trigger this? Any ideas for how to troubleshoot further? When I swap out boost::thread with std::thread, the SIGSEGV goes away. So far I haven't been able to reproduce the error with a simple example. I am using boost 1.84.0
Thread 5 "a.out" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe8704700 (LWP 700154)]
_dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:126
126 ../sysdeps/x86_64/dl-trampoline.h: No such file or directory.
(gdb) bt
#0 _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:126
#1 0x0000000006869d48 in boost::detail::set_current_thread_data(boost::detail::thread_data_base*) ()
#2 0x000000000686af07 in thread_proxy ()
#3 0x00007ffff77761da in start_thread () from /lib64/libpthread.so.0
#4 0x00007ffff361a8d3 in clone () from /lib64/libc.so.6
- Dominant language
- C++
- Stars
- 213
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from boostorg/thread
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
Similar issues
-
ai_reviewed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ydb-platform/ydb#53869 · 3 comments ·
-
bug cert blocker needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
project-chip/connectedhomeip#74373 ·
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31035 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
vllm-project/vllm-ascend#17329 ·