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 18:36:45 +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
--- Comment #5 from David Smith <dsmith at redhat dot com> ---
(In reply to Josh Stone from comment #4)
> (In reply to Martin Cermak from comment #0)
> > kernel-3.13.0-0.rc7.31.sa2.bz1094366.aarch64 (3.13.0-0.rc7.31 + rhbz1094366 fix)
>
> This kernel does have CONFIG_COMPAT=y, but I don't think that's typical for
> that product. Regardless, we need to be prepared for the possibility.
Here's the description for CONFIG_COMPAT from the kernel's arm/arm64/Kconfig
file:
====
This option enables support for a 32-bit EL0 running under a 64-bit
kernel at EL1. AArch32-specific components such as system calls,
the user helper functions, VFP support and the ptrace interface are
handled appropriately by the kernel.
If you want to execute 32-bit userspace applications, say Y.
====
So right now the kernel supports 32-bit apps, but the toolchain doesn't. Odd,
but OK.
>From poking around the kernel source, it appears that on arm64, syscall numbers
for 32-bit syscalls can differ from their 64-bit versions, but most are the
same.
I've checked in commit 48ad5c5 which should hopefully fix this.
Martin or Josh, I'll need one of you to test this and let me know if it worked.
--
You are receiving this mail because:
You are the assignee for the bug.