From: David Ahern <dsahern@gmail.com>
To: Milian Wolff <mail@milianw.de>, "Frank Ch. Eigler" <fche@redhat.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Access to backtraces from user-space tracepoint callback in perf-script?
Date: Sat, 17 May 2014 08:31:55 -0600 [thread overview]
Message-ID: <537772DB.3060406@gmail.com> (raw)
In-Reply-To: <2081629.cxlLP7Yh7G@minime>
On 5/17/14, 5:24 AM, Milian Wolff wrote:
> On Friday 16 May 2014 11:57:02 Frank Ch. Eigler wrote:
>> Milian Wolff <mail@milianw.de> writes:
>>> [...]
>>>
>>>>>> today I played around with perf-script(-python) and custom
>>>>>> tracepoints.
>>>>>> What I could not figure out so far is how to print a backtrace from
>>>>>> the
>>>>>> python callback. [...]
>>
>> While you wait, you might try systemtap, wherein there exists support
>> not just for plain C-level backtracing (print_ubacktrace() as for any
>> other program), but also python source-level backtracing (via a tapset
>> function).
>>
>> https://sourceware.org/systemtap/examples/#general/py2example.stp
>
> Hey,
>
> thanks for the hint. But I never got SystemTap to work on any of my machines
> :-/
>
> For now I'll stick to manual libunwind + libbacktrace + LD_PRELOAD tracing.
> But I'd love to see this available in perf eventually.
>
Did you try the patch to perf? Does it give you access to the callchain
in python scripts like you want?
David
prev parent reply other threads:[~2014-05-17 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 15:44 Access to backtraces from user-space tracepoint callback in perf-script? Milian Wolff
2014-05-07 12:46 ` Milian Wolff
2014-05-14 0:33 ` Namhyung Kim
2014-05-14 8:47 ` Milian Wolff
2014-05-16 15:57 ` Frank Ch. Eigler
2014-05-17 11:24 ` Milian Wolff
2014-05-17 14:31 ` David Ahern [this message]
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=537772DB.3060406@gmail.com \
--to=dsahern@gmail.com \
--cc=fche@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mail@milianw.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;
as well as URLs for NNTP newsgroup(s).