stacktrace
stacktrace copied to clipboard
C++ library for storing and printing backtraces.
Hello, I'm trying to cross build boost for M1 on an Intel mac. Everything goes fine, except addr2line does not build. From the configuration check, it shows ``` - libbacktrace...
It's a bit more lightweight than dbgeng/windbg (I think it's used by them) and it wouldn't have the issues with COM (It's what Rust uses for backtraces in the MSVC...
Resolve #121 See the [documentation](https://docs.microsoft.com/windows-hardware/drivers/ddi/dbgeng/nf-dbgeng-debugcreate#remarks): > You don't need to call **CoInitialize**, **CoInitializeEx**, or **OleInitialize** to use this function and interfaces obtained by it. Even if DIA support is implemented,...
If **BOOST_STACKTRACE_USE_WINDBG** is defined, the implementation of `stacktrace::to_string` opens a new WinDbg session each time without ending the previous one which results in leaking memory (see #111). This PR adds...
https://github.com/boostorg/stacktrace/blob/75b7986f9799184ecd679d86273532cb54e6a0dc/include/boost/stacktrace/detail/frame_msvc.ipp#L60 `CoInitializeEx` is superfluous for DbgEng.h interfaces. These interfaces are COM-like, not completely COM compliant interfaces, and they don't use COM apartments. It is now official - see https://github.com/MicrosoftDocs/windows-driver-docs-ddi/pull/1256#issuecomment-1031922715 The...
Not sure if it is really needed, as perf gain and simplification are both very small. Referring to this: https://github.com/boostorg/stacktrace/blob/75b7986f9799184ecd679d86273532cb54e6a0dc/include/boost/stacktrace/detail/frame_msvc.ipp#L222-L234 According to the updated [IDebugSymbols::GetNameByOffset documentation](https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/dbgeng/nf-dbgeng-idebugsymbols-getnamebyoffset), sizes will include the...
I recently downloaded Boost 1.78, but when building it for Linux using: ``` ./bootstrap.sh --with-python=/usr/bin/python3 --with-libraries=all ./b2 --layout=versioned cxxflags="-fPIC" toolset=gcc variant=release link=shared,static threading=multi runtime-link=shared install ``` I noticed the following...
Hello, currently boost-stacktrace with the `backtrace` backend will call [backtrace_create_state](https://github.com/boostorg/stacktrace/blob/08d720adbd01c0187af256eb491cffece7e87857/include/boost/stacktrace/detail/libbacktrace_impls.hpp#L104) once for each thread. This creates a memory leak since each time a new thread is created, a new `backtrace_state`...
Hello! Thanks for wonderful library. I use it on windows platform successfully. I tried to use on android platform but without success. Addresses are printed but ndk-stack can't symbolicate. example...
Just build the simplest example: ```cpp #include #include "boost/stacktrace/stacktrace.hpp" using namespace std; int main() { cout