This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/16914] probe syscall.* fails with compilation error
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 06 May 2014 14:30:10 +0000
- Subject: [Bug translator/16914] probe syscall.* fails with compilation error
- Auto-submitted: auto-generated
- References: <bug-16914-6586 at http dot sourceware dot 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.