From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16914] New: probe syscall.* fails with compilation error
Date: Tue, 06 May 2014 14:00:00 -0000 [thread overview]
Message-ID: <bug-16914-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16914
Bug ID: 16914
Summary: probe syscall.* fails with compilation error
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
Created attachment 7588
--> https://sourceware.org/bugzilla/attachment.cgi?id=7588&action=edit
stap output
On aarch64, stap -e 'probe syscall.* { log("hey!"); exit() }' returns errors
like this:
/tmp/stapV76Au7/stap_19d2b02d95ec8b13d55cf356928e49ab_143230_src.c: In function
‘probe_2344’:
/tmp/stapV76Au7/stap_19d2b02d95ec8b13d55cf356928e49ab_143230_src.c:11776:43:
error: ‘__NR_compat_clone’ undeclared (first use in this function)
if ((((l->l___nr) != ((((int64_t) ( __NR_compat_clone ))))))) {
^
/tmp/stapV76Au7/stap_19d2b02d95ec8b13d55cf356928e49ab_143230_src.c:11776:43:
note: each undeclared identifier is reported only once for each function it
appears in
/tmp/stapV76Au7/stap_19d2b02d95ec8b13d55cf356928e49ab_143230_src.c: In function
‘probe_2346’:
/tmp/stapV76Au7/stap_19d2b02d95ec8b13d55cf356928e49ab_143230_src.c:11907:43:
error: ‘__NR_compat_close’ undeclared (first use in this function)
if ((((l->l___nr) != ((((int64_t) ( __NR_compat_close ))))))) {
^
/tmp/stapV76Au7/stap_19d2b02d95ec8b13d55cf356928e49ab_143230_src.c: In function
‘probe_2356’:
/tmp/stapV76Au7/stap_19d2b02d95ec8b13d55cf356928e49ab_143230_src.c:12038:43:
error: ‘__NR_compat_futimesat’ undeclared (first use in this function)
if ((((l->l___nr) != ((((int64_t) ( __NR_compat_futimesat ))))))) {
[ ... ]
# rpm -q kernel systemtap
kernel-3.13.0-0.rc7.31.sa2.bz1094366.aarch64 (3.13.0-0.rc7.31 + rhbz1094366
fix)
systemtap-2.6-1.sa1.3.aarch64 (fresh upstream master head)
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-05-06 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 14:00 mcermak at redhat dot com [this message]
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
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@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).