systemtap script mutex-contention.stp fails due to ambiguous process path
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemtap (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I tried to run systemtap with the mutex-contentio
/usr/share/
I ran systemtap like this:
-------
ben@bearded-
Pass 1: parsed user script and 91 library script(s) using 94020virt/
semantic error: while resolving probe point: identifier 'process' at /usr/share/
source: probe process(
semantic error: glob /lib*/libc.so* error (3)
semantic error: while resolving probe point: identifier 'process' at :58:7
source: probe process(
semantic error: glob /lib*/libpthrea
semantic error: while resolving probe point: identifier 'process' at :59:7
source: probe process(
Pass 2: analyzed script: 3 probe(s), 146 function(s), 7 embed(s), 15 global(s) using 296144virt/
Pass 2: analysis failed. [man error::pass2]
Tip: /usr/share/
-------
Since this script comes in the examples, it carries some expectation that it should work with the distribution that provided it.
The error message is quite confusing, until I realised that I have multiple libc.so files on my system:
ben@bearded-
/lib/i386-
/lib/x86_
/usr/lib/
Therefore I created a test stp script where I specified the full path to libc.so.6 (see test-mutex-
I expect that this problem will also affect other example scripts as well. It seems that systemtap needs a set of unit tests to cover the examples!
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: systemtap 2.2.1-1ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Thu Mar 27 13:19:35 2014
InstallationDate: Installed on 2013-09-13 (194 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
SourcePackage: systemtap
UpgradeStatus: Upgraded to saucy on 2014-01-15 (70 days ago)
Changed in systemtap (Ubuntu): | |
status: | New → Confirmed |