public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16960] New: today's fresh bits do not work correctly on RHEL6
Date: Mon, 19 May 2014 14:34:00 -0000	[thread overview]
Message-ID: <bug-16960-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=16960

            Bug ID: 16960
           Summary: today's fresh bits do not work correctly on RHEL6
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: mcermak at redhat dot com

Today's master head bits do not work correctly on RHEL6. They compile fine, but
stap throws:


 6.5 S x86_64 # stap -v -e 'probe kernel.function("vfs_read"){ log("hey!");
exit() }'
Pass 1: parsed user script and 106 library script(s) using
205180virt/32988res/3128shr/30452data kb, in 220usr/10sys/229real ms.
Pass 2: analyzed script: 1 probe(s), 2 function(s), 0 embed(s), 0 global(s)
using 233928virt/62272res/3752shr/59200data kb, in 430usr/90sys/524real ms.
Pass 3: translated to C into
"/tmp/stap5OIzNd/stap_21128e6f690f827280eb0960a3fccd4f_1173_src.c" using
233928virt/62600res/4080shr/59200data kb, in 0usr/70sys/74real ms.
In file included from /usr/share/systemtap/runtime/linux/runtime.h:210,
                 from /usr/share/systemtap/runtime/runtime.h:24,
                 from
/tmp/stap5OIzNd/stap_21128e6f690f827280eb0960a3fccd4f_1173_src.c:24:
/usr/share/systemtap/runtime/linux/task_finder.c: In function
‘__stp_utrace_attach_match_filename’:
/usr/share/systemtap/runtime/linux/task_finder.c:850: error: implicit
declaration of function ‘from_kuid_munged’
In file included from /usr/share/systemtap/runtime/linux/print.c:17,
                 from /usr/share/systemtap/runtime/print.c:17,
                 from /usr/share/systemtap/runtime/runtime_context.h:22,
                 from
/tmp/stap5OIzNd/stap_21128e6f690f827280eb0960a3fccd4f_1173_src.c:52:
/usr/share/systemtap/runtime/transport/transport.c: In function
‘_stp_transport_init’:
/usr/share/systemtap/runtime/transport/transport.c:353: error: implicit
declaration of function ‘from_kgid_munged’
make[1]: *** [/tmp/stap5OIzNd/stap_21128e6f690f827280eb0960a3fccd4f_1173_src.o]
Error 1
make: *** [_module_/tmp/stap5OIzNd] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compiled C into "stap_21128e6f690f827280eb0960a3fccd4f_1173.ko" in
6070usr/1250sys/7863real ms.
Pass 4: compilation failed.  [man error::pass4]
 6.5 S x86_64 # 


Some logs (and also built packages in an xz tarball) available at
https://url.corp.redhat.com/a4aba4f

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2014-05-19 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 14:34 mcermak at redhat dot com [this message]
2014-05-21 18:22 ` [Bug translator/16960] " dsmith at redhat dot com
2014-05-21 19:11 ` 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-16960-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).