Crash on an Aarch64 based Yocto Linux system with valgrind 3.18.1:

==4065== Parent PID: 1
==4065== 
ARM64 front end: branch_etc
disInstr(arm64): unhandled instruction 0xD50B7A22
disInstr(arm64): 1101'0101 0000'1011 0111'1010 0010'0010
==4065== valgrind: Unrecognised instruction at address 0x8f24da0.
==4065==    at 0x8F24DA0: ??? (in /usr/lib/libmali.so.0.31.0)
==4065== Your program just tried to execute an instruction that Valgrind
==4065== did not recognise.  There are two possible reasons for this.
==4065== 1. Your program has a bug and erroneously jumped to a non-code
==4065==    location.  If you are running Memcheck and you just saw a
==4065==    warning about a bad jump, it's probably your program's fault.
==4065== 2. The instruction is legitimate but Valgrind doesn't handle it,
==4065==    i.e. it's Valgrind's fault.  If you think this is the case or
==4065==    you are not sure, please let us know and we'll try to fix it.
==4065== Either way, Valgrind will now raise a SIGILL signal which will
==4065== probably kill your program.
==4065== 
==4065== Process terminating with default action of signal 4 (SIGILL): dumping core
==4065==  Illegal opcode at address 0x8F24DA0
==4065==    at 0x8F24DA0: ??? (in /usr/lib/libmali.so.0.31.0)
==4065== 
==4065== HEAP SUMMARY:
==4065==     in use at exit: 47,496,772 bytes in 209,756 blocks
==4065==   total heap usage: 874,472 allocs, 664,716 frees, 209,946,412 bytes allocated
==4065== 
==4065== For a detailed leak analysis, rerun with: --leak-check=full
==4065== 
==4065== For lists of detected and suppressed errors, rerun with: -s
==4065== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 7 from 2)


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION