gcc/libbacktrace
Ian Lance Taylor 3e2f329e94 libbacktrace: check for objcopy --add-gnu-debuglink using --help
* configure.ac: Check for objcopy --add-gnu-debuglink by using
	objcopy --help.
	* configure: Regenerate
2021-02-11 18:10:25 -08:00
..
aclocal.m4
alloc.c
allocfail.c
allocfail.sh
atomic.c
backtrace-supported.h.in
backtrace.c
backtrace.h
btest.c
ChangeLog
ChangeLog.jit
config.h.in
configure libbacktrace: check for objcopy --add-gnu-debuglink using --help 2021-02-11 18:10:25 -08:00
configure.ac libbacktrace: check for objcopy --add-gnu-debuglink using --help 2021-02-11 18:10:25 -08:00
dwarf.c
edtest2.c
edtest.c
elf.c
fileline.c
filetype.awk
install-debuginfo-for-buildid.sh.in
instrumented_alloc.c
internal.h
macho.c
Makefile.am
Makefile.in
mmap.c
mmapio.c
mtest.c
nounwind.c
pecoff.c
posix.c
print.c
read.c
README
simple.c
sort.c
state.c
stest.c
test_format.c
testlib.c
testlib.h
ttest.c
unittest.c
unknown.c
xcoff.c
xztest.c
ztest.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.