This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: python tracing
- From: Stan Cox <scox at redhat dot com>
- To: systemtap at sourceware dot org
- Date: Wed, 10 Apr 2013 11:28:22 -0400
- 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>,<5162DB45 dot 20501 at redhat dot com> <46C9AEB13B3AC04C82D760CC817521714604636F at SRV363 dot tudelft dot net>,<51641687 dot 4030900 at redhat dot com> <46C9AEB13B3AC04C82D760CC81752171460464E6 at SRV363 dot tudelft dot net> <516430B1 dot 5070206 at redhat dot com> <059601ce353a$15041f10$3f0c5d30$ at bezemer@tudelft.nl>
We test a variation of this in the upstream systemtap testsuite
(testsuite/systemtap.apps/python.exp) What the test does is: fetch
upstream python sources, apply either one of python2.patch or
python3.patch, build python, run test using a scenario similar to the
following:
stap celsius-var.stp -c "python -sS celsius.py 30" '*' python.log
stap celsius-var.stp -c "python3 -sS celsius.py 30" '*' python.log