From: "Chí-Thanh Christopher Nguyễn" <chithanh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] New global USE flag: unwind
Date: Thu, 11 May 2017 11:29:44 +0200 [thread overview]
Message-ID: <8020c939-22ae-5b4f-1dc8-cb767b0484ce@gentoo.org> (raw)
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.
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.
Best regards,
Chí-Thanh Christopher Nguyễn
next reply other threads:[~2017-05-11 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 9:29 Chí-Thanh Christopher Nguyễn [this message]
2017-05-11 10:21 ` [gentoo-dev] [RFC] New global USE flag: unwind Mart Raudsepp
2017-05-11 10:39 ` Michał Górny
2017-05-11 11:05 ` Chí-Thanh Christopher Nguyễn
2017-05-18 7:51 ` Chí-Thanh Christopher Nguyễn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8020c939-22ae-5b4f-1dc8-cb767b0484ce@gentoo.org \
--to=chithanh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox