From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] latrace: provide demangling support
Date: Thu, 1 Dec 2016 09:22:57 +0100 [thread overview]
Message-ID: <20161201082257.19747-1-jbe@pengutronix.de> (raw)
To support demangeling, latrace requires libiberty. Demangeling is requiered
for C++ only (AFAIR), so let it be an option.
Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
---
rules/latrace.in | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/rules/latrace.in b/rules/latrace.in
index 8aa6ae9..4ee5265 100644
--- a/rules/latrace.in
+++ b/rules/latrace.in
@@ -1,8 +1,21 @@
## SECTION=debug_tools
-config LATRACE
+menuconfig LATRACE
tristate
- prompt "latrace"
+ prompt "latrace "
+ select BINUTILS if LATRACE_DEMANGLE
help
A tool to trace library calls and get their statistics in a
manner similar to the strace utility
+
+if LATRACE
+
+config LATRACE_DEMANGLE
+ bool
+ prompt "demangle supprt"
+ default y
+ help
+ Enable support for the demangle feature, required to trace C++ libraries
+ for example.
+
+endif
--
2.10.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2016-12-01 8:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20161201082257.19747-1-jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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