You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 1024 seems suspect. In fact, QEMU does not support this syscall anymore as of qemu/qemu@13756fb0, which landed in v2.6.0. This makes the unsupported syscall 1024 that has been popping up make more sense.
I think the best way to handle it is to have aarch64/linux/open.asm which uses the SYS_openat syscall.
The text was updated successfully, but these errors were encountered:
* Remove unavailable syscalls from AArch64
The Linux kernel has apparently stopped supporting these
* Rewrite shellcraft.aarch64.linux.cat, add open which uses openat
Fixes#896
* Fix doctests to use openat
While working on #883, one of the failing tests is
cat
for aarch64, because__NR_open
is not defined in MUSL's headers for aarch64.At first this seemed like a bug, but our current syscalls for it are e.g.:
The 1024 seems suspect. In fact, QEMU does not support this syscall anymore as of qemu/qemu@13756fb0, which landed in v2.6.0. This makes the
unsupported syscall 1024
that has been popping up make more sense.I think the best way to handle it is to have
aarch64/linux/open.asm
which uses theSYS_openat
syscall.The text was updated successfully, but these errors were encountered: