For anyone following along at home, I’ve replicated this with Oracle Linux 8 on an Ampere cloud instance on Oracle Cloud:
$ snap run --strace snapcraft init
[pid 41377] execve("/var/lib/snapd/snap/snapcraft/6956/bin/python", ["/var/lib/snapd/snap/snapcraft/69"..., "/snap/snapcraft/6956/bin/snapcra"..., "init"], 0x400007b860 /* 48 vars */ <unfinished ...>
[pid 41379] <... futex resumed>) = ?
[pid 41379] +++ exited with 0 +++
[pid 41378] +++ exited with 0 +++
[pid 41380] +++ exited with 0 +++
/usr/bin/strace: Process 41381 attached
[pid 41381] +++ exited with 0 +++
<... execve resumed>) = -1 EINVAL (Invalid argument)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=NULL} ---
+++ killed by SIGSEGV +++
error: signal: segmentation fault
Edit: This is strange:
$ file /var/lib/snapd/snap/snapcraft/6956/usr/bin/python3.8
/var/lib/snapd/snap/snapcraft/6956/usr/bin/python3.8: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, BuildID[sha1]=356168b7ac8384a8cec914d8e4fa9abf3b6b938e, stripped
$ ldd /var/lib/snapd/snap/snapcraft/6956/usr/bin/python3.8
not a dynamic executable