cpptrace icon indicating copy to clipboard operation
cpptrace copied to clipboard

Simple, portable, and self-contained stacktrace library for C++11 and newer

Results 27 cpptrace issues
Sort by recently updated
recently updated
newest added

Compiling with `-Wpedantic` reveals a significant number of warnings surrounding the use of the assertion macros in `utils/error.hpp`. It seems that invoking such a macro without at least one argument...

question

Currently it's impossible to to choose libunwind (not the gcc one but stand-alone one - the one that's signal safe) through Conan. I had to patch Conanfile to achieve it:...

enhancement
conan

In #84 a stack trace was shown which included symbols that didn't make sense. I've had another user mention to me odd symbols in trace output on windows. I have...

help wanted
more information needed

This pull request enables Bazel build support for cpptrace. Please note that currently, only Linux is supported. Additional platform support will be added if necessary. To build with bazel, simply...

Are you interested in supporting Bazel as an additional build system for this project? Bazel is a powerful build tool that offers many advantages, such as fast incremental builds, a...

enhancement

Zstd has fixed the warning produced by CMake for min versions lower than 3.5. See https://github.com/facebook/zstd/pull/3807.

enhancement

Would be nice to get even (partial) support for Emscripten -- I currently only need `cpptrace::generate_trace().print()` in my project, and I have to `#ifdef` for Emscripten like this: ```cpp #ifdef...

enhancement
help wanted
new platform
backlog

![image](https://github.com/user-attachments/assets/850df0c9-929e-4952-8cf1-45134c1673c6) I would really liked it if those features were implemented: - [ ] Omit function parameters, only print the namespace/name - [ ] Add source base dir. So it...

enhancement

Follow-up to #164. Possibilities include: - - [ ] ~~Parameter filtering~~ - - [ ] ~~Template parameter filtering~~ - - [ ] ~~Some attempt to parse the function names from...

enhancement

If you've got nested `CPPTRACE_TRY`/`CPPTRACE_CATCH` blocks, like this: ```c++ CPPTRACE_TRY { foo(); with_opentelemetry_sub_span([](){ CPPRACE_TRY { bar(); CPPTRACE_CATCH(const std::exception &e) { put_exception_on_opentelemetry_span(e, cpptrace::from_current_exception()); throw; } }); baz(); } CPPTRACE_CATCH(const std::exception &e)...

enhancement
resolved in next release