Stacktrace with backtrace to display files and lines #2298
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Detailed information in https://www.boost.org/doc/libs/develop/doc/html/stacktrace/configuration_and_build.html
The
BOOST_STACKTRACE_USE_BACKTRACE
option was the only reliable one here, but should be tested across a variety of configurations if possible. There is a callout for clang but setting a custom path for the file is not supported here - haven't tested with clang.NANO_STACKTRACE_BACKTRACE
cmake option. If enabled, will link againstlibbacktrace
and define theBOOST_STACKTRACE_USE_BACKTRACE
macro where necessary, except on Windows which already has good default stacktrace--debug_stacktrace
CLI option to easily see what will be the usual stacktraceExample output: