This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug testsuite/16473] New: rlimit.exp: adjust for weak symbols
- From: "jlebon at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 20 Jan 2014 22:48:38 +0000
- Subject: [Bug testsuite/16473] New: rlimit.exp: adjust for weak symbols
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=16473
Bug ID: 16473
Summary: rlimit.exp: adjust for weak symbols
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: systemtap at sourceware dot org
Reporter: jlebon at redhat dot com
Since support for weak symbols was added (commits 91bb908 and 0035051, also see
bug 10208), the rlimit.exp test fails as follow:
Running ../../systemtap/testsuite/systemtap.base/rlimit.exp ...
FAIL: rlimit unlimited
FAIL: rlimit AS increase (as root)
FAIL: rlimit AS realistic
FAIL: rlimit CPU increase (as root)
FAIL: rlimit CPU realistic
FAIL: rlimit NPROC increase (as root)
FAIL: rlimit NPROC realistic
FAIL: rlimit STACK increase (as root)
FAIL: rlimit STACK realistic
FAIL: rlimit FSIZE increase (as root)
FAIL: rlimit FSIZE realistic
The reason is that the rlimit.stp script is defined as:
probe kernel.function("*ar*").call { println($$vars) }
And this pattern now matches many weak symbols (especially those suffixed with
e.g. '.part.xx'). These weak symbols don't seem to have any variables
accessible, and we thus get errors when trying to resolve $$vars. This is the
kind of error we get:
[vm build]$ stap -e 'probe process("/lib*/libc.so.*").function("chmod") {
println($$vars) }' -p4
semantic error: unresolved target-symbol expression: identifier '$$vars' at
<input>:1:62
source: probe process("/lib*/libc.so.*").function("chmod") {
println($$vars) }
^
Pass 2: analysis failed. [man error::pass2]
[vm build]$
If this is an issue with weak symbols not giving access to $$vars when it
should, then bug 10208 should be re-opened, and this one closed. If this is an
issue with rlimit.stp being too enthusiastic, then we should change the pattern
to make it more restrictive.
--
You are receiving this mail because:
You are the assignee for the bug.