The Rust `ring` crate -- which is used in several ports (list further down) -- can bork on -current (amd64; on both AMD and Intel hardware). I am not sure of the precise reason, but I would hazard a guess that it's due to noexec.
If I clone the repository (https://github.com/briansmith/ring) and `cargo test`: $ cargo test Running unittests src/lib.rs (target/debug/deps/ring-359bb067476182bf) running 90 tests error: test failed, to rerun pass `--lib` Caused by: process didn't exit successfully: `/tmp/ring/target/debug/deps/ring-359bb067476182bf` (signal: 11, SIGSEGV: invalid memory reference) If I gdb it: $ gdb /tmp/ring/target/debug/deps/ring-359bb067476182bf ... (gdb) run ring_core_0_17_0_not_released_yet_aes_hw_set_encrypt_key () at /tmp/ring/target/debug/build/ring-fb208db87823020c/out/aesni-x86_64-elf.S:924 924 movdqa .Lkey_rotate(%rip),%xmm5 This *might* be a ports problem because several ports include the `ring` crate: www/zola/ www/nextcloud_notify_push/ www/libreddit/ security/vaultwarden/ sysutils/rustic/ security/sn0int/ security/rbw/ net/routinator/ mail/stalwart/cli/ mail/stalwart/imap/ mail/stalwart/jmap/ mail/meli/ devel/maturin/ audio/ncspot/ Unfortunately I don't use any of them, so I don't know if they use `ring` in a way that can cause a crash or not. Maintainers / users might find it worth checking? Laurie
