• https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290411 reports that 15.0 does not support __syscall use in armv7 lib32 code on aarch64; but armv7 chroot fails too

    From Mark Millard@marklmi@yahoo.com to muc.lists.freebsd.stable on Tue Oct 21 13:46:20 2025
    From Newsgroup: muc.lists.freebsd.stable

    QUOTE
    While debugging a devel/libunwind failure in an armv7 program running on aarch64,
    I found that the program crashes with ENOSYS while calling __syscall(). Here 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.
    END QUOTE
    But I just tested trying the program in a chroot to an armv7
    world directory tree and it fails there too. It is not just
    lib32 that fails.
    ===
    Mark Millard
    marklmi at yahoo.com
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2