Ühel kenal päeval, N, 11.05.2017 kell 11:29, kirjutas Chí-Thanh Christopher Nguyễn: > Suggested description: Add support for stack traces and function > name > resolution via sys-libs/libunwind > > That description is a little unwieldy though, better suggestions are > welcome.
I think it's usually used to be able to grab function names and such for crash backtraces or whatnot into logs, even if the binaries are rather optimized? > Currently in use by the following packages: > > dev-cpp/glog:unwind - Use sys-libs/libunwind for stack unwinding > instead > of glibc/gcc (may be more reliable on x86_64) > dev-libs/efl:unwind - Enable debug support via sys-libs/libunwind > dev-libs/weston:unwind - Enable libunwind usage for backtraces > dev-util/ltrace:unwind - Use sys-libs/libunwind for frame unwinding > support > dev-util/perf:unwind - Use sys-libs/libunwind for frame unwinding > support. > dev-util/strace:unwind - Enable stack backtraces (-k flag) via > sys-libs/libunwind > media-libs/gstreamer:unwind - Enable sys-libs/libunwind usage for > better > backtrace support in leaks tracer module > www-apache/mod_backtrace:unwind - Use sys-libs/libunwind to provide > better resolution of function names. > x11-apps/intel-gpu-tools:unwind - Provide automatic stack traces on > test > failures > x11-base/xorg-server:unwind - Enable libunwind usage for backtraces > > I understand that dev-cpp/glog uses the unwind flag differently from > the > other packages. If that is an issue that package's flag could be > renamed > to "libunwind" as sys-libs/libcxx et al. currently use. For gstreamer 1.12 I will also need one for libdw for DWARF unwind to avoid automagic deps. Maybe it'd be OK to control both (and so both libraries) via USE=unwind too instead of some local USE=dwarf or USE=libdw or USE=dw or whatnot? Mart
