public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
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 14:30:00 -0000	[thread overview]
Message-ID: <bug-16914-6586-D3VuVWxz6T@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16914-6586@http.sourceware.org/bugzilla/>

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

David Smith <dsmith at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dsmith at redhat dot com

--- Comment #2 from David Smith <dsmith at redhat dot com> ---
(In reply to Martin Cermak from comment #0)
> Created attachment 7588 [details]
> 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 ))))))) {

I understand what is going on here, but I need some aarch64 education to know
how to fix it. Does aarch64 run 32-bit executables? Is the CONFIG_COMPAT option
on on an aarch64 kernel?

If so, aarch64 will need its own section in runtime/linux/compat_unistd.h.

If not, something wacky is going on and that code should have never been hit.

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

  parent reply	other threads:[~2014-05-06 14:30 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 [this message]
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-D3VuVWxz6T@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).