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

[Tom <tgrom.automail%nuegia.net@localhost>]

The following reply was made to PR port-arm/55119; it has been noted by GNATS.

From: Tom <tgrom.automail%nuegia.net@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-arm/55119: mutt segfaults on start
Date: Sat, 28 Mar 2020 09:29:30 -0700

 On Sat, 28 Mar 2020 09:45:02 +0000 (UTC)
 Martin Husemann <martin%duskware.de@localhost> wrote:
 
 > The following reply was made to PR port-arm/55119; it has been noted
 > by GNATS.
 > 
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc: 
 > Subject: Re: port-arm/55119: mutt segfaults on start
 > Date: Sat, 28 Mar 2020 10:42:14 +0100
 > 
 >  On Sat, Mar 28, 2020 at 09:40:01AM +0000, tgrom.automail%nuegia.net@localhost
 > wrote:
 >  > Program received signal SIGILL, Illegal instruction.
 >  > 0x0000f9918ab4a128 in _armv8_pmull_probe ()
 >  > from /usr/lib/libcrypto.so.14 (gdb) bt
 >  > #0  0x0000f9918ab4a128 in _armv8_pmull_probe ()
 >  > from /usr/lib/libcrypto.so.14 #1  0x0000f9918ab4a478 in
 >  > OPENSSL_cpuid_setup () from /usr/lib/libcrypto.so.14  
 >  
 >  This is not a SEGFAULT and it is harmless (the library catches it).
 >  It is used to probe for arm features to enable optimized crypto code.
 >  
 >  You can continue in gdb at that point and everything should run
 > normally. 
 >  Martin
 >  
 
 How would I continue without gdb, because otherwise the program stops
 and generates a core dump. I can send you a coredump if that would be
 useful.