Nim wrapper for libbacktrace
Go to file
Ștefan Talpalaru 84b40137bb
prevent getBacktrace() from being inlined
2019-12-21 11:34:18 +01:00
tests support Windows by using the bundled libunwind 2019-12-20 03:03:12 +01:00
vendor initial commit 2019-12-18 02:09:27 +01:00
.appveyor.yml support Windows by using the bundled libunwind 2019-12-20 03:03:12 +01:00
.gitignore initial commit 2019-12-18 02:09:27 +01:00
.gitmodules initial commit 2019-12-18 02:09:27 +01:00
.travis.yml initial commit 2019-12-18 02:09:27 +01:00
LICENSE-APACHEv2 initial commit 2019-12-18 02:09:27 +01:00
LICENSE-MIT initial commit 2019-12-18 02:09:27 +01:00
Makefile debugging support 2019-12-20 19:06:29 +01:00
README.md debugging support 2019-12-20 19:06:29 +01:00
libbacktrace.nim prevent getBacktrace() from being inlined 2019-12-21 11:34:18 +01:00
libbacktrace.nimble support Windows by using the bundled libunwind 2019-12-20 03:03:12 +01:00
libbacktrace_wrapper.c more debugging info 2019-12-21 11:25:43 +01:00
libbacktrace_wrapper.cpp support Windows by using the bundled libunwind 2019-12-20 03:03:12 +01:00
libbacktrace_wrapper.h more debugging info 2019-12-21 11:25:43 +01:00
libbacktrace_wrapper.nim more debugging info 2019-12-21 11:25:43 +01:00

README.md

All the backtrace, none of the overhead

Build Status Build status License: Apache License: MIT Stability: experimental

Nim's default stack tracing functionality comes with significant overhead, by adding nimln_(), nimfr_() calls all over the place. The problem is being discussed upstream in this GitHub issue.

That popFrame() at the end of each C function is particularly problematic, since it prevents the C compiler from doing tail-call optimisations.

This is a lightweight alternative based on libbacktrace, meant to offer the same stack traces without the runtime overhead.

C++ function name demangling is supported using "__cxa_demangle()".

Building & Testing

This project uses Git submodules, so get it with:

git clone https://github.com/status-im/nim-libbacktrace.git
cd nim-libbacktrace
git submodule update --init

You build the library (or libraries, on macOS) with make. You test it with make test.

Nimble is grudgingly supported, so nimble install works. (No, we will not let a silly package manager dictate our project's structure. People have the power!)

Supported platforms

Tested with GCC and LLVM on Linux, macOS and 64-bit Windows (with Mingw-w64 and the MSYS that comes with "Git for Windows").

Usage

bttest.nim:

import libbacktrace

# presumably in some procedure:
echo getBacktrace()

# Should be the same output as writeStackTrace() - minus the header.
# When the C compiler inlines some procs, libbacktrace might get confused with proc names,
# but it gets the files and line numbers right nonetheless.

We need debugging symbols in the binary and we can do without Nim's bloated and slow stack trace implementation:

nim c -f --debugger:native --stacktrace:off bttest.nim

If you're unfortunate enough to need this on macOS, there's an extra step for creating debugging symbols:

dsymutil bttest

Now you can run it:

./bttest

Debugging

export NIM_LIBBACKTRACE_DEBUG=1 to see the trace lines hidden by default.

Dependencies

You need Make, CMake and, of course, Nim up and running.

The other dependencies are bundled, for your convenience. We use a libbacktrace fork with macOS support and LLVM's libunwind variant that's needed on macOS and Windows.

If you know better and want to use your system's libbacktrace package instead of the bundled one, you can, with make USE_SYSTEM_LIBS=1 and by passing -d:libbacktraceUseSystemLibs to the Nim compiler.

How does libbacktrace work on systems without libunwind installed, I hear you asking? It uses GCC's basic unwind support in libgcc_s.so.1 - that runtime's so good that even Clang links it by default ;-)

To get the running binary's path in a cross-platform way, we rely on whereami.

License

Licensed and distributed under either of

or

at your option. These files may not be copied, modified, or distributed except according to those terms.