RE: python tracing

[Cor-paul Bezemer - EWI <C dot Bezemer at tudelft dot nl>]

You are right, the tapset was missing.
I used this one: http://packaging-farm.dachary.org/packaging-farm/fedora/x86_64/f14/root/usr/share/systemtap/tapset/libpython2.7-64.stp

but am getting the error 
 ./stap test_python.stp --runtime=dyninst -c'~/Play/python/python2.7-2.7.4~rc1/build-shared/python test.py'
semantic error: while resolving probe point: identifier 'process' at /home/corpaul/stap/share/systemtap/tapset/python.stp:12:32
        source: probe python.function.return = process("python").library("/usr/lib64/libpython2.7.so.1.0").mark("function__return")
                                               ^

semantic error: no match
semantic error: while resolving probe point: identifier 'python' at test_python.stp:1:7
        source: probe python.function.return 
                      ^

Pass 2: analysis failed.  [man error::pass2]

--CP
________________________________________
From: David Smith [dsmith@redhat.com]
Sent: Monday, April 08, 2013 4:14 PM
To: Cor-paul Bezemer - EWI
Cc: systemtap@sourceware.org
Subject: Re: python tracing

On 04/08/2013 08:11 AM, corpaul wrote:
> 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

I haven't done traced python with systemtap, but from the error it looks
like there is supposed to be a systemtap python tapset file (probably
named something like 'python.stp') that is supposed to be added to
systemtap.

Did that exist somewhere in those patches?

--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)