stacktrace_from_exception on non-x86
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the non-x86 build with the bootstrap.sh and b2 commands in the issue. Read src/exception_headers.h and src/from_exception.cpp, including is_libcpp_runtime, to trace the architecture and runtime checks. Done means the stacktrace library builds on non-x86 with GCC/libstdc++ without requiring the listed workarounds.
Written by the indexing model from the issue text.
Description
I submitted the below to the mailing list, but I wanted to re-iterate it here for more eyes. https://lists.boost.org/Archives/boost/2024/04/256604.php
This feature is guarded by BOOST_STACKTRACE_ALWAYS_STORE_IN_PADDING, but that is only enabled on x86.
This means that
./bootstrap.sh --with-toolset=gcc --with-libraries=stacktrace
./b2 install threading=multi toolset=gcc
always fails to build on non-x86 platforms. There are three current workarounds:
- set boost.stacktrace.from_exception=off
- set BOOST_STACKTRACE_LIBCXX_RUNTIME_MAY_CAUSE_MEMORY_LEAK
- build with threading=single
(1) prevents me from using this feature. (2) shouldn't be needed on it's face because I'm using gcc/libstdc++. (3) affects more than stacktrace.
Is this an incidental error, or is there a reason I wasn't able to deduce as to why this feature can't be used on non-x86+libstdc++?
It seems like the check for libc++ on non-x86 can't be entirely done at compile time. I definitely understand wanting to alert users to the dangers of using this feature, but there also doesn't seem to be a good way of detecting the presence of libc++ at compile time (hence the need for is_libcpp_runtime).
- Dominant language
- C++
- Stars
- 497
- Forks
- 86
- Avg merge
- 8d 20h
- Merged PRs (30d)
- 3
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/stacktrace
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
boostorg/stacktrace#233 ·
-
Ошибка в Inscape Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
boostorg/stacktrace#211 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
boostorg/stacktrace#208 · 6 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
boostorg/stacktrace#197 · 3 comments ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 25/100
boostorg/stacktrace#176 · 1 comment ·
All issues in boostorg/stacktrace
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 ·