This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: python tracing


On 04/08/2013 09:41 AM, Cor-paul Bezemer - EWI wrote:
> 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]

OK, we're getting a bit further now.

Can you try the following command? This should show us what tracepoints
stap thinks are present in your python executable.

# stap -L
'process("python").library("/usr/lib64/libpython2.7.so.1.0").mark("*")'

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]