This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: python tracing
- From: David Smith <dsmith at redhat dot com>
- To: Cor-paul Bezemer - EWI <C dot Bezemer at tudelft dot nl>
- Cc: "systemtap at sourceware dot org" <systemtap at sourceware dot org>
- Date: Mon, 08 Apr 2013 09:59:17 -0500
- Subject: Re: python tracing
- References: <1365426684043-227721 dot post at n7 dot nabble dot com>,<5162D0AC dot 7050505 at redhat dot com> <46C9AEB13B3AC04C82D760CC81752171460461CE at SRV363 dot tudelft dot net>
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)