From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/21403] provide something like ppfunc() that also provided the class name of the function
Date: Thu, 20 Apr 2017 19:51:00 -0000 [thread overview]
Message-ID: <bug-21403-6586-OjdA7sEQ2Z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21403-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21403
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
(In reply to David Smith from comment #0)
> It would be nice if there was a way for a function to not just return the
> function name the current probe point, but also the class name (assuming
> we're in a C++ class).
>
> The problem here is that the pp() information (which is what ppfunc()
> parses) has the class name, but in a mangled format. We'd have to add a C++
> demangler for this to work properly.
Just to be clear here, I'm not suggesting we put a C++ demangler in the kernel
modules. I'm suggesting that we add enough code to the translator to put the
unmangled C++ class/function name ("CLASS::FUNCTION") as part of the probe
point name field the translator emits. Then a ppfunc() variant could extract
CLASS::FUNCTION from the full probe name field.
(Note that we'd still have mangled C++ names in backtraces that would need to
be passed through c++filt to get demangled.)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-04-20 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 13:57 [Bug translator/21403] New: " dsmith at redhat dot com
2017-04-20 19:51 ` dsmith at redhat dot com [this message]
2017-05-09 0:02 ` [Bug translator/21403] " fche at redhat dot com
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=bug-21403-6586-OjdA7sEQ2Z@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).