Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-22 Thread Harry Schmalzbauer
Am 22.02.2019 um 04:51 schrieb Eugene Grosbein: 21.02.2019 22:27, Harry Schmalzbauer wrote: The object is clearly corrupted. Thanks to your hint to readelf, I found out that it gets corrupted during dump(8) (or resotore, not yet analyzed). The obj tree contains the good version, the dump arc

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-21 Thread Eugene Grosbein
21.02.2019 22:27, Harry Schmalzbauer wrote: >> The object is clearly corrupted. > > Thanks to your hint to readelf, I found out that it gets corrupted during > dump(8) (or resotore, not yet analyzed). > The obj tree contains the good version, the dump archive not. > The dump archive is used as s

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-21 Thread Harry Schmalzbauer
Am 21.02.2019 um 10:36 schrieb Konstantin Belousov: … ELF Header: Magic: 7f 45 4c 46 02 01 01 09 00 00 00 00 00 00 00 00 Class: ELF64 Data: 2's complement, little endian Version: 1 (current)

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-21 Thread Patrick M. Hausen
Hello, I don’t know if this is related or not, but when I compile the Nextcloud client port https://svnweb.freebsd.org/ports/head/deskutils/nextcloudclient/ on 11.2 by setting DEFAULT_VERSIONS+=ssl=openssl111 it dumps core, too. Kind regards Patrick -- punkt.de GmbH

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-21 Thread Konstantin Belousov
On Thu, Feb 21, 2019 at 10:03:29AM +0100, Harry Schmalzbauer wrote: > Am 21.02.2019 um 09:54 schrieb Konstantin Belousov: > > On Thu, Feb 21, 2019 at 09:24:43AM +0100, Harry Schmalzbauer wrote: > >> Am 20.02.2019 um 17:51 schrieb Harry Schmalzbauer: > >>> Hello, > >>> > >> … > >>> gdb shows: > >>>

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-21 Thread Harry Schmalzbauer
Am 21.02.2019 um 09:54 schrieb Konstantin Belousov: On Thu, Feb 21, 2019 at 09:24:43AM +0100, Harry Schmalzbauer wrote: Am 20.02.2019 um 17:51 schrieb Harry Schmalzbauer: Hello, … gdb shows: Core was generated by `/usr/sbin/auditdistd'. Program terminated with signal 11, Segmentation fault.

Re: Strange rtld-elf failure on stable/12 [Was: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)]

2019-02-21 Thread Konstantin Belousov
On Thu, Feb 21, 2019 at 09:24:43AM +0100, Harry Schmalzbauer wrote: > Am 20.02.2019 um 17:51 schrieb Harry Schmalzbauer: > > Hello, > > > … > > gdb shows: > > Core was generated by `/usr/sbin/auditdistd'. > > Program terminated with signal 11, Segmentation fault. > > Reading symbols from /lib/libut

Strange rtld-elf failure on stable/12 [Was: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)]

2019-02-21 Thread Harry Schmalzbauer
Am 20.02.2019 um 17:51 schrieb Harry Schmalzbauer: Hello, … gdb shows: Core was generated by `/usr/sbin/auditdistd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libutil.so.9...Reading symbols from /usr/lib/debug//lib/libutil.so.9.debug...done. done. Loade

libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-20 Thread Harry Schmalzbauer
Hello, I'm tryint to upgrade a bhyve guest from stable/11 to stable/12. pkg(8) for example crashes with signal 11. I looked for other binaries affected by ldd /usr/sbin/* | & grep 'signal 11$' wich gives /usr/sbin/auditdistd: signal 11 /usr/sbin/bhyve: signal 11 /usr/sbin/bsnmpd: signal /usr/sb