On Fri, Jan 27, 2017 at 03:31:28PM +0100, Stephane Bortzmeyer <[email protected]> wrote a message of 19 lines which said:
> Program received signal SIGILL, Illegal instruction. This one was spurious (and it is documented in the OpenSSL FAQ <https://www.openssl.org/docs/faq.html#PROG17>). The real signal (SIGSEGV, as indicated in the original bug report) is here: (gdb) handle SIGILL nostop Signal Stop Print Pass to program Description SIGILL No Yes Yes Illegal instruction (gdb) run -H my.host.example -6 -c 'check_disks' Starting program: /usr/lib/nagios/plugins/check_nrpe -H my.host.example -6 -c 'check_disks' Program received signal SIGILL, Illegal instruction. Program received signal SIGSEGV, Segmentation fault. 0xb6d96926 in _int_free (av=0xb6e307a4 <main_arena>, p=0x7f5910f0, have_lock=0) at malloc.c:4049 4049 malloc.c: No such file or directory. (gdb) (gdb) where #0 0xb6d96926 in _int_free (av=0xb6e307a4 <main_arena>, p=0x7f5910f0, have_lock=0) at malloc.c:4049 #1 0xb6e99472 in CRYPTO_free () from /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.2 #2 0xb6ebdc04 in BN_clear_free () from /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.2 Backtrace stopped: previous frame identical to this frame (corrupt stack?)
