https://bugs.kde.org/show_bug.cgi?id=358620
--- Comment #4 from Jeffrey Walton <noloa...@gmail.com> ---
> This is with 3.7.0, which is really old now. Can you try again with 3.11.0 or
> better with the current SVN trunk?
The issue is present when building 3.11 from sources:
raspberrypi:botan$ valgrind ./botan-test
==6661== Memcheck, a memory error detector
==6661== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==6661== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==6661== Command: ./botan-test
==6661==
disInstr(arm): unhandled instruction: 0xF1010200
cond=15(0xF) 27:20=16(0x10) 4:4=0 3:0=0(0x0)
==6661== valgrind: Unrecognised instruction at address 0x486b6f4.
==6661== at 0x486B6F4: ??? (in /usr/lib/arm-linux-gnueabihf/libarmmem.so)
==6661== Your program just tried to execute an instruction that Valgrind
==6661== did not recognise. There are two possible reasons for this.
==6661== 1. Your program has a bug and erroneously jumped to a non-code
==6661== location. If you are running Memcheck and you just saw a
==6661== warning about a bad jump, it's probably your program's fault.
==6661== 2. The instruction is legitimate but Valgrind doesn't handle it,
==6661== i.e. it's Valgrind's fault. If you think this is the case or
==6661== you are not sure, please let us know and we'll try to fix it.
==6661== Either way, Valgrind will now raise a SIGILL signal which will
==6661== probably kill your program.
==6661==
==6661== Process terminating with default action of signal 4 (SIGILL)
==6661== Illegal opcode at address 0x486B6F4
==6661== at 0x486B6F4: ??? (in /usr/lib/arm-linux-gnueabihf/libarmmem.so)
It looks like the issue affects a lot of folks:
http://www.google.com/search?q="unhandled+instruction%3A+0xF1010200";
--
You are receiving this mail because:
You are watching all bug changes.
