From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16914] probe syscall.* fails with compilation error
Date: Tue, 06 May 2014 20:05:00 -0000 [thread overview]
Message-ID: <bug-16914-6586-FpNKa3Dncg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16914-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16914
--- Comment #7 from David Smith <dsmith at redhat dot com> ---
I found an aarch64 machine I could access
(running3.13.0-0.rc7.31.sa2.k32v1.aarch64.debug), built, installed, and got the
following:
====
# stap -p4 -e 'probe syscall.* { log("hey!"); exit() }'
In file included from
/usr/src/kernels/3.13.0-0.rc7.31.sa2.k32v1.aarch64.debug/arch/arm64/include/asm/dma-mapping.h:27:0,
from include/linux/dma-mapping.h:76,
from include/linux/skbuff.h:33,
from include/linux/netlink.h:6,
from
/tmp/stapSX3Lm0/stap_a9d73a0f48c94b332f8efe28f9c0739d_104773_src.c:127:
/usr/src/kernels/3.13.0-0.rc7.31.sa2.k32v1.aarch64.debug/arch/arm64/include/asm/xen/hypervisor.h:1:50:
fatal error: ../../arm/include/asm/xen/hypervisor.h: No such file or directory
#include <../../arm/include/asm/xen/hypervisor.h>
^
compilation terminated.
make[1]: ***
[/tmp/stapSX3Lm0/stap_a9d73a0f48c94b332f8efe28f9c0739d_104773_src.o] Error 1
make: *** [_module_/tmp/stapSX3Lm0] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed. [man error::pass4]
====
So that looks like a kernel problem, not a systemtap problem.
On your kernel, something odd is going on if things like __NR_open aren't
defined. Can you try the following patch and see if that fixes things?
====
diff --git a/runtime/linux/compat_unistd.h b/runtime/linux/compat_unistd.h
index 25ca1bd..11abc26 100644
--- a/runtime/linux/compat_unistd.h
+++ b/runtime/linux/compat_unistd.h
@@ -11,6 +11,8 @@
#ifndef _COMPAT_UNISTD_H_
#define _COMPAT_UNISTD_H_
+#include <linux/unistd.h>
+
#if defined(__x86_64__)
// On older kernels (like RHEL5), we have to define our own 32-bit
====
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-05-06 20:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 14:00 [Bug translator/16914] New: " mcermak at redhat dot com
2014-05-06 14:00 ` [Bug translator/16914] " mcermak at redhat dot com
2014-05-06 14:30 ` dsmith at redhat dot com
2014-05-06 17:46 ` mcermak at redhat dot com
2014-05-06 18:17 ` jistone at redhat dot com
2014-05-06 18:36 ` dsmith at redhat dot com
2014-05-06 19:42 ` mcermak at redhat dot com
2014-05-06 20:05 ` dsmith at redhat dot com [this message]
2014-05-06 20:23 ` mcermak at redhat dot com
2014-05-06 20:44 ` dsmith at redhat dot com
2015-02-12 16:36 ` aram.h at mgk dot ro
2015-02-12 17:34 ` dsmith at redhat dot com
2015-02-12 18:18 ` aram.h at mgk dot ro
2015-02-12 19:07 ` dsmith at redhat dot com
2015-02-12 21:10 ` aram.h at mgk dot ro
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-16914-6586-FpNKa3Dncg@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).