vasilito
48a924c561
The libredox 0.1.19 / redox_syscall 0.9.1 bump left 45 recipe lockfiles pinning libredox 0.1.18+rb0.3.1 and redox_syscall 0.9.0+rb0.3.1. The cookbook builds with --locked, so every affected recipe died with error: cannot update the lock file .../Cargo.lock because --locked was passed to prevent this which is what took out redox-driver-sys -- and with it every Red Bear driver -- during the redbear-full build. Regenerating the fork lockfiles was not enough; the recipes that consume the forks as path deps carry their own. This is step 6 of local/docs/FORK-BUMP-PATCHING-POLICY.md applied to the recipe layer. Also drop the hardcoded GCC version in recipes/libs/libstdcxx-v3: the literal include/c++/13.2.0 stopped resolving the moment the cross toolchain moved to 16.1.0, leaving -I pointing at a directory that does not exist. Now resolves the newest installed C++ header directory and fails loudly if there is none. Same failure class as the hardcoded 13.2.0 in mk/prefix.mk. Note: a few recipe-level Cargo.lock files (redox-driver-pci, cpufreqd, redbear-acmd/-ecmd/-ftdi) sit beside a recipe.toml whose [source] is path = "source", so they are not build inputs; redox-driver-pci's even references a redox-driver-core/Cargo.toml that does not exist. They are left alone rather than given meaning they do not have. redox-driver-sys now cooks clean.
42 lines
1.9 KiB
Plaintext
42 lines
1.9 KiB
Plaintext
The libbacktrace library
|
|
Initially written by Ian Lance Taylor <iant@golang.org>
|
|
|
|
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.
|
|
|
|
In general the functions provided by this library are async-signal-safe,
|
|
meaning that they may be safely called from a signal handler.
|
|
That said, on systems that use dl_iterate_phdr, such as GNU/Linux,
|
|
the first call to a libbacktrace function will call dl_iterate_phdr,
|
|
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.
|
|
|
|
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 July 2024, libbacktrace supports ELF, PE/COFF, Mach-O, and
|
|
XCOFF executables with DWARF debugging information.
|
|
In other words, it supports GNU/Linux, *BSD, macOS, Windows, and AIX.
|
|
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
|
|
https://itanium-cxx-abi.github.io/cxx-abi/abi-eh.html
|
|
This API is provided by GCC and clang.
|