This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
python tracing
- From: corpaul <c dot bezemer at tudelft dot nl>
- To: systemtap at sourceware dot org
- Date: Mon, 8 Apr 2013 06:11:24 -0700 (PDT)
- Subject: python tracing
Was anyone here successful on python tracing?
I patched Python 2.7 using the patches on http://bugs.python.org/issue13405
Now when I try to run
http://sourceware.org/systemtap/wiki/PythonMarkers?action=AttachFile&do=view&target=systemtap-example.stp
, I get the error:
semantic error: while resolving probe point: identifier 'python' at
stap-python.stp:11:7
source: probe python.function.entry
^
semantic error: probe point mismatch (alternatives: begin begin(number) end
end(number) error error(number) kernel kprobe module(string) netfilter never
perf process process(number) process(string) procfs procfs(string) stap
staprun timer): identifier 'python' at :11:7
source: probe python.function.entry
^
semantic error: while resolving probe point: identifier 'python' at :16:7
source: probe python.function.return
^
semantic error: probe point mismatch (alternatives: begin begin(number) end
end(number) error error(number) kernel kprobe module(string) netfilter never
perf process process(number) process(string) procfs procfs(string) stap
staprun timer): identifier 'python' at :16:7
source: probe python.function.return
^
Pass 2: analysis failed. [man error::pass2]
Does this mean that Python was not patched correctly? or do i need to change
something in Systemtap?
Thanks!
--CP
--
View this message in context: http://sourceware-org.1504.n7.nabble.com/python-tracing-tp227721.html
Sent from the Sourceware - systemtap mailing list archive at Nabble.com.