8581b59fb3
Fixes #45731 libbacktrace uses mmap if available to map ranges of the files containing debug information. On macOS `mmap` will succeed even if the mapped range does not exist, and a SIGBUS (with an unusual EXC_BAD_ACCESS code 10) will occur when the program attempts to page in the memory. To combat this we force `libbacktrace` to be built with the simple `read` based fallback on Apple platforms. |
||
---|---|---|
.. | ||
aclocal.m4 | ||
alloc.c | ||
ansidecl.h | ||
atomic.c | ||
backtrace-supported.h.in | ||
backtrace.c | ||
backtrace.h | ||
btest.c | ||
ChangeLog | ||
ChangeLog.jit | ||
config.h.in | ||
config.sub | ||
configure | ||
configure.ac | ||
dwarf2.def | ||
dwarf2.h | ||
dwarf.c | ||
elf.c | ||
fileline.c | ||
filenames.h | ||
filetype.awk | ||
hashtab.h | ||
install-sh | ||
internal.h | ||
ltmain.sh | ||
macho.c | ||
Makefile.am | ||
Makefile.in | ||
mmap.c | ||
mmapio.c | ||
nounwind.c | ||
pecoff.c | ||
posix.c | ||
print.c | ||
read.c | ||
README | ||
simple.c | ||
sort.c | ||
state.c | ||
stest.c | ||
unknown.c |
The libbacktrace library Initially written by Ian Lance Taylor <iant@google.com> 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. 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. As of September 2012, libbacktrace only supports ELF executables with DWARF debugging information. The library is written to make it straightforward to add support for other object file and debugging formats.