This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug dyninst/15061] New: stapdyn missing process.library.mark probe hits
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 24 Jan 2013 16:29:47 +0000
- Subject: [Bug dyninst/15061] New: stapdyn missing process.library.mark probe hits
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15061
Bug #: 15061
Summary: stapdyn missing process.library.mark probe hits
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: dyninst
AssignedTo: systemtap@sourceware.org
ReportedBy: dsmith@redhat.com
Classification: Unclassified
While adding dyninst support to several testcases (commit 5acb534), I
investigated some odd failures with the systemtap.base/library.exp testcase. To
simplify things, let's avoid the testcase itself, but use its test programs.
(Note that the testcase has several failures with the linux runtime on modern
kernels, since there is no 'process.function.return' probe support yet.)
The following command should build the test programs - the vebose (-v) option
will cause the testcase to not clean up its test programs.
====
# cd testsuite
# make installcheck RUNTESTFLAGS="-v library.exp"
... stuff deleted ...
====
OK, now we've got the test programs (sdt_misc.x and libsdt.so).
With the linux runtime, we get the following:
====
# stap -e 'probe process("sdt_misc.x").library("libsdt.so").mark("*") {
printf("mark %s\n", $$name) }' -c ./sdt_misc.x
mark test_probe_2
mark test_probe_2
mark test_probe_0
mark test_probe_3
mark test_probe_4
mark test_probe_1
====
With the dyninst runtime, we get:
====
# stap --runtime=dyninst -e 'probe
process("sdt_misc.x").library("libsdt.so").mark("*") { printf("mark %s\n",
$$name) }' -c ./sdt_misc.x
mark test_probe_2
mark test_probe_1
====
So, the dyninst runtime missed 4 mark probe hits.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.