From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/16555] New: on rawhide, we're getting errors in the task.stp tapset
Date: Tue, 11 Feb 2014 15:10:00 -0000 [thread overview]
Message-ID: <bug-16555-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16555
Bug ID: 16555
Summary: on rawhide, we're getting errors in the task.stp
tapset
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
We're getting errors in the task.stp tapset (which are unfortunately masked by
builok.exp):
# stap -vp4 ../src/testsuite/buildok/task-embedded.stp
Pass 1: parsed user script and 101 library script(s) using
210536virt/28044res/2924shr/25620data kb, in 180usr/30sys/217real ms.
Pass 2: analyzed script: 1 probe(s), 25 function(s), 1 embed(s), 0 global(s)
using 357172virt/31212res/4052shr/27396data kb, in 1020usr/620sys/1703real ms.
Pass 3: translated to C into
"/tmp/stap3fopDv/stap_baa033f011836befd470d85f53b241db_10845_src.c" using
357172virt/31460res/4300shr/27396data kb, in 10usr/0sys/2real ms.
/tmp/stap3fopDv/stap_baa033f011836befd470d85f53b241db_10845_src.c: In function
‘function_task_egid’:
/tmp/stap3fopDv/stap_baa033f011836befd470d85f53b241db_10845_src.c:1068:19:
error: incompatible types when assigning to type ‘int64_t’ from type ‘kgid_t’
STAP_RETVALUE = task_egid (t);
^
/tmp/stap3fopDv/stap_baa033f011836befd470d85f53b241db_10845_src.c: In function
‘function_task_euid’:
/tmp/stap3fopDv/stap_baa033f011836befd470d85f53b241db_10845_src.c:1112:19:
error: incompatible types when assigning to type ‘int64_t’ from type ‘kuid_t’
STAP_RETVALUE = task_euid (t);
^
/tmp/stap3fopDv/stap_baa033f011836befd470d85f53b241db_10845_src.c: In function
‘function_task_gid’:
/tmp/stap3fopDv/stap_baa033f011836befd470d85f53b241db_10845_src.c:1214:19:
error: incompatible types when assigning to type ‘int64_t’ from type ‘kgid_t’
STAP_RETVALUE = task_gid (t);
^
/tmp/stap3fopDv/stap_baa033f011836befd470d85f53b241db_10845_src.c: In function
‘function_task_uid’:
/tmp/stap3fopDv/stap_baa033f011836befd470d85f53b241db_10845_src.c:1628:19:
error: incompatible types when assigning to type ‘int64_t’ from type ‘kuid_t’
STAP_RETVALUE = task_uid (t);
^
make[1]: ***
[/tmp/stap3fopDv/stap_baa033f011836befd470d85f53b241db_10845_src.o] Error 1
make: *** [_module_/tmp/stap3fopDv] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compiled C into "stap_baa033f011836befd470d85f53b241db_10845.ko" in
8130usr/1680sys/10133real ms.
Pass 4: compilation failed. [man error::pass4]
====
These errors are all because uids/gids are no longer simple types.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-02-11 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 15:10 dsmith at redhat dot com [this message]
2014-02-11 15:14 ` [Bug tapsets/16555] " dsmith at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-16555-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).