2016-09-10 07:26:00 -07:00
|
|
|
# libbacktrace
|
|
|
|
|
A C library that may be linked into a C/C++ program to produce symbolic backtraces
|
2016-09-10 07:59:09 -07:00
|
|
|
|
2018-01-24 18:36:47 -08:00
|
|
|
Initially written by Ian Lance Taylor <iant@golang.org>.
|
|
|
|
|
|
|
|
|
|
This is version 1.0.
|
|
|
|
|
It is likely that this will always be version 1.0.
|
2016-09-10 07:59:09 -07:00
|
|
|
|
|
|
|
|
The libbacktrace library may be linked into a program or library and
|
|
|
|
|
used to produce symbolic backtraces.
|
|
|
|
|
Sample uses would be to print a detailed backtrace when an error
|
|
|
|
|
occurs or to gather detailed profiling information.
|
2024-07-17 17:06:51 -07:00
|
|
|
|
2020-10-26 13:45:23 -07:00
|
|
|
In general the functions provided by this library are async-signal-safe,
|
|
|
|
|
meaning that they may be safely called from a signal handler.
|
2024-07-17 17:06:51 -07:00
|
|
|
That said, on systems that use `dl_iterate_phdr`, such as GNU/Linux,
|
2024-10-20 16:56:59 -07:00
|
|
|
the first call to a libbacktrace function will call `dl_iterate_phdr`,
|
2024-07-17 17:06:51 -07:00
|
|
|
which is not in general async-signal-safe. Therefore, programs
|
|
|
|
|
that call libbacktrace from a signal handler should ensure that they
|
|
|
|
|
make an initial call from outside of a signal handler.
|
|
|
|
|
Similar considerations apply when arranging to call libbacktrace
|
|
|
|
|
from within malloc; `dl_iterate_phdr` can also call malloc,
|
|
|
|
|
so make an initial call to a libbacktrace function outside of
|
|
|
|
|
malloc before trying to call libbacktrace functions within malloc.
|
2016-09-10 07:59:09 -07:00
|
|
|
|
|
|
|
|
The libbacktrace library is provided under a BSD license.
|
|
|
|
|
See the source files for the exact license text.
|
|
|
|
|
|
|
|
|
|
The public functions are declared and documented in the header file
|
|
|
|
|
backtrace.h, which should be #include'd by a user of the library.
|
|
|
|
|
|
|
|
|
|
Building libbacktrace will generate a file backtrace-supported.h,
|
|
|
|
|
which a user of the library may use to determine whether backtraces
|
|
|
|
|
will work.
|
|
|
|
|
See the source file backtrace-supported.h.in for the macros that it
|
|
|
|
|
defines.
|
|
|
|
|
|
2024-07-17 17:06:51 -07:00
|
|
|
As of July 2024, libbacktrace supports ELF, PE/COFF, Mach-O, and
|
2020-10-26 13:45:23 -07:00
|
|
|
XCOFF executables with DWARF debugging information.
|
|
|
|
|
In other words, it supports GNU/Linux, *BSD, macOS, Windows, and AIX.
|
2016-09-10 07:59:09 -07:00
|
|
|
The library is written to make it straightforward to add support for
|
|
|
|
|
other object file and debugging formats.
|
|
|
|
|
|
|
|
|
|
The library relies on the C++ unwind API defined at
|
2017-05-29 11:48:14 -07:00
|
|
|
https://itanium-cxx-abi.github.io/cxx-abi/abi-eh.html
|
2020-10-26 13:45:23 -07:00
|
|
|
This API is provided by GCC and clang.
|