This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: probing C++, Java, etc.
- From: Josh Stone <jistone at redhat dot com>
- To: Jim Keniston <jkenisto at linux dot vnet dot ibm dot com>
- Cc: SystemTap <systemtap at sources dot redhat dot com>
- Date: Wed, 07 Apr 2010 16:36:51 -0700
- Subject: Re: probing C++, Java, etc.
- References: <1270681500.2893.256.camel@localhost>
On 04/07/2010 04:05 PM, Jim Keniston wrote:
> Has the stap team done anything special to support C++ tracing -- e.g.,
> name demangling, convenient access to C++ string values?
See PR10461. For the most part it's the same as C, with the addition of
namespace::class::function scoping in probe points. The debuginfo names
aren't mangled, which makes it a little easier, but we've talked about
maybe re-mangling names for brevity in pp() (possibly leaving it to the
user to pipe through c++filt). Convenient access to strings is on my
"bonus" list, but it hasn't been done.
I think what we have for C++ is mostly Good Enough, but if I start
seeing requests it may re-energize me to do more... :)
> Any other languages I should mention, besides C? Any other neat stap
> features that build on uprobes?
There are a few other packages built for static markers in Fedora, see:
https://fedoraproject.org/wiki/Features/SystemtapStaticProbes
Josh