Oh I'm so silly, it appears I simply canceled the program seeing the
SIGILL warning assuming it was just about to crash when I just would
have needed to let it run. Thanks so much for explaining :-)
For what it's worth, this is on an ARM64 Allwinner/PinePhone 1.2 CE 3GB
RAM edition, so an early ARM64 architecture. I usually only use valgrind
on my x64 desktop where there isn't any such SIGILL stuff, so that's why
I'm not very familiar with it.
On 6/26/22 10:52 AM, Tom Hughes wrote:
On 26/06/2022 09:13, ellie wrote:
How do I run openssl programs in valgrind on processors where it
causes SIGILL? https://www.openssl.org/docs/faq.html#PROG17
In what way is it not working?
When valgrind encounters an instruction it doesn't understand it
logs the details and then passes the SIGILL to and signal handler
which the application has registered exactly as openssl appears
to be expecting.
Are you sure the SIGILL you're seeing is caused by openssl processor
feature detection and isn't just some other random instruction that
valgrind doesn't implement yet? What architecture is this?
Tom
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
