re: toolchain/53643: gdb on core files fails on arm

[matthew green <mrg%eterna.com.au@localhost>]

The following reply was made to PR toolchain/53643; it has been noted by GNATS.

From: matthew green <mrg%eterna.com.au@localhost>
To: gnats-bugs%NetBSD.org@localhost, martin%netbsd.org@localhost
Cc: toolchain-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
    netbsd-bugs%netbsd.org@localhost
Subject: re: toolchain/53643: gdb on core files fails on arm
Date: Sun, 30 Sep 2018 13:45:32 +1000

 > The new openssl does not work well on arm. I get various core files, but
 > looking at them seems to be unreliable:
 > 
 > Core was generated by `ssh-add'.
 > Program terminated with signal SIGILL, Illegal instruction.
 > #0  0x6f559468 in _armv7_tick () from /usr/lib/libcrypto.so.14
 > (gdb) bt
 > #0  0x6f559468 in _armv7_tick () from /usr/lib/libcrypto.so.14
 > Register 25 is not available
 > 
 > Note that even the pc register is likely wrong - the instruction it points
 > at is not illegal on this cpu, and tracing through the call in live
 > instances does not throw a SIGILL.
 
 are there any CFI markers in the asm?  there isn't for x86 last
 i saw, and they're needed for properly traversing stack traces
 into these asm files.  i'd guess that's probably the problem..
 
 
 .mrg.