- split configure options into multiple lines for easy of editing
- add systemtap static markers (wcohen, mjw, dmalcolm; patch 8), a
systemtap tapset defining "python.function.entry" and
"python.function.return" to make the markers easy to use (dmalcolm;
source 5), and an example of using the tapset to the docs (dmalcolm;
source 6) (rhbz:545179)
This commit is contained in:
parent
d5a5bf3c65
commit
c969609dfe
4 changed files with 435 additions and 2 deletions
19
systemtap-example.stp
Normal file
19
systemtap-example.stp
Normal file
|
|
@ -0,0 +1,19 @@
|
|||
/*
|
||||
Example usage of the Python systemtap tapset to show a nested view of all
|
||||
Python function calls (and returns) across the whole system.
|
||||
|
||||
Run this using
|
||||
stap systemtap-example.stp
|
||||
to instrument all Python processes on the system, or (for example) using
|
||||
stap systemtap-example.stp -c COMMAND
|
||||
to instrument a specific program (implemented in Python)
|
||||
*/
|
||||
probe python.function.entry
|
||||
{
|
||||
printf("%s => %s in %s:%d\n", thread_indent(1), funcname, filename, lineno);
|
||||
}
|
||||
|
||||
probe python.function.return
|
||||
{
|
||||
printf("%s <= %s in %s:%d\n", thread_indent(-1), funcname, filename, lineno);
|
||||
}
|
||||
Loading…
Add table
Add a link
Reference in a new issue