Date: Tue, 21 Oct 2025 20:26:20 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 290411] lib32: __syscall() not supported Message-ID: <bug-290411-7@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D290411 Bug ID: 290411 Summary: lib32: __syscall() not supported Product: Base System Version: 15.0-CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: fuz@FreeBSD.org Flags: mfc-stable15?, mfc-stable14? While debugging a devel/libunwind failure in an armv7 program running on aarch64, I found that the program crashes with ENOSYS while calling __syscall(). He= re is a reproducer: #include <sys/mman.h> #include <sys/syscall.h> #include <unistd.h> int main() { __syscall(SYS_mmap, 0, 4096, 3, MAP_ANON|MAP_PRIVATE, -1, 0); } This is effectively what the GET_MEMORY() macro in libunwind does. Expected output: nothing. Actual output: Bad system call (core dumped). I'll work around this failure in libunwind for now, but please fix this for= the future. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-290411-7>