On 7/29/2015 11:04 PM, John Reiser wrote:
>> disInstr(arm): unhandled instruction: 0xEEBA0BEF
>>                    cond=14(0xE) 27:20=235(0xEB) 4:4=0 3:0=15(0xF)
>
> You can help even more by telling us which hardware you have.
> For instance, this is an original RaspberryPi B+:
> -----
> $ cat /proc/cpuinfo
> processor     : 0
> model name    : ARMv6-compatible processor rev 7 (v6l)
> BogoMIPS      : 2.00
> Features      : half thumb fastmult vfp edsp java tls
> CPU implementer       : 0x41
> CPU architecture: 7
> CPU variant   : 0x0
> CPU part      : 0xb76
> CPU revision  : 7
>
> Hardware      : BCM2708
> Revision      : 0010
> -----
>
> If you create a file with the unhandled instruction, and compile and 
> disassemble it,
> then you can see what the instruction is:
> -----foo.s
>       .word 0xEEBA0BEF
> -----
> $ gcc -c foo.s
> $ gdb foo.o
> (gdb) x/i 0
> 0: vcvt.f64.s32  d0, d0, #1
> (gdb)

If we are really talking about the ARM processor, this instruction is
supposedly handled:

https://bugs.kde.org/show_bug.cgi?id=308717

Regards -- Eliot Moss

------------------------------------------------------------------------------
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to