This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug testsuite/15625] New: unprivileged_embedded_C test confused by stub registers.stp
- From: "jkenisto at us dot ibm.com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 13 Jun 2013 23:41:01 +0000
- Subject: [Bug testsuite/15625] New: unprivileged_embedded_C test confused by stub registers.stp
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15625
Bug ID: 15625
Summary: unprivileged_embedded_C test confused by stub
registers.stp
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: systemtap at sourceware dot org
Reporter: jkenisto at us dot ibm.com
When running the systemtap.unprivileged/unprivileged_embedded_C.exp test, I see
the following failure:
...
testing s64_arg (long);no embedded C
testing u64_arg (long);no embedded C
testing asmlinkage();no embedded C
testing fastcall();no embedded C
testing regparm(long);no embedded C
eval exec stap -p2 --privilege=stapusr -e {probe begin { regparm(0) }}
semantic error: function may not be used when --privilege=stapusr is specified:
identifier 'regparm' at /usr/share/systemtap/tapset/i386/registers.stp:245:10
source: function regparm(n:long) %{
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
funcname is regparm
FAIL: unprivileged embedded C: no embedded C: --privilege=stapusr:
regparm(long)
stap correctly detects that regparm() in tapset/i386/registers.stp uses
embedded C,** but the test is looking at tapset/registers.stp, which contains
only stub functions with no embedded C.
A fix is to have the test ignore the stub registers.stp.
**Should the functions in registers.stp be marked unprivileged? They provide
read-only access to CPU registers and function args.
--
You are receiving this mail because:
You are the assignee for the bug.