|
From: Lu M. <kin...@gm...> - 2013-09-17 21:45:39
|
Hello all, I use valgrind 3.8.1 with an arm executable. However the valgrind output the error message: ==1276== disInstr(arm): unhandled instruction: 0xEEFA0BEF cond=14(0xE) 27:20=239(0xEF) 4:4=0 3:0=15(0xF) ==1276== valgrind: Unrecognised instruction at address 0x25afc. ==1276== at 0x25AFC: crude_dragon_weakness (in /home/spec_exe/445.gobmk/exe/gobmk_base.armhf-gcc47) ==1276== Your program just tried to execute an instruction that Valgrind ==1276== did not recognise. There are two possible reasons for this. ==1276== 1. Your program has a bug and erroneously jumped to a non-code ==1276== location. If you are running Memcheck and you just saw a ==1276== warning about a bad jump, it's probably your program's fault. ==1276== 2. The instruction is legitimate but Valgrind doesn't handle it, ==1276== i.e. it's Valgrind's fault. If you think this is the case or ==1276== you are not sure, please let us know and we'll try to fix it. ==1276== Either way, Valgrind will now raise a SIGILL signal which will ==1276== probably kill your program. ==1276== ==1276== Process terminating with default action of signal 4 (SIGILL) ==1276== Illegal opcode at address 0x25AFC ==1276== at 0x25AFC: crude_dragon_weakness (in /home/spec_exe/445.gobmk/exe/gobmk_base.armhf-gcc47) I disassemble the executable and find out that the illegal instruction is vcvt.f64.s32 d16, d16, #1. I am wondering whether vcvt.f64.s32 is unsupported under valgrind or I have misuse valgrind? Thanks a lot |