On 5/17/14, 5:24 AM, Milian Wolff wrote:
On Friday 16 May 2014 11:57:02 Frank Ch. Eigler wrote:
Milian Wolff <m...@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
--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
