Re: port-arm/55119 (mutt segfaults on start)

[riastradh%NetBSD.org@localhost]

Synopsis: mutt segfaults on start

State-Changed-From-To: open->closed
State-Changed-By: riastradh%NetBSD.org@localhost
State-Changed-When: Thu, 17 Apr 2025 21:41:07 +0000
State-Changed-Why:
It looks like this issue is actually just OpenSSL's CPU feature
detection, which works by

1. installing a SIGILL signal handler, and then
2. trying a SIMD/crypto instruction to see if it's supported.

If it's supported, great; if not, it triggers SIGILL, and the signal
handler longjmps out.  This is perfectly normal -- but when you run it
under gdb, gdb traps the SIGILL itself, so it looks like the program
crashes.

If it's crashing and dumping core _outside_ gdb, please feel free to
follow up with more details.  For example, maybe you can get a stack
trace out of a core dump:

arm64$ mutt
Segmentation fault (core dumped)
arm64$ gdb mutt ./mutt.core
(gdb) bt

But if you're just seeing the SIGILL under gdb, that's not a bug --
that's how it's supposed to work.