[Valgrind-users] Unrecognized instruction at address

[M Rajesh-B. <B2...@fr...>]

Hi,

I tried to use  valgrind-3.6.1 memcheck tool for platform ppc32-linux,
I cross compiled(CC=powerpc-none-linux-gnuspe-gcc) on my host(Ubuntu) and copied to target board.

But I facing error indicated as "valgrind: Unrecognised instruction at address 0x4018ff0",
Not only my program, I am getting similar error for any other program so thinking that there is no issue with my program.

Following is the log generated
==2069== Memcheck, a memory error detector
==2069== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==2069== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info
==2069== Command: /root/pspmaster -f
==2069== Parent PID: 2063
==2069==
disInstr(ppc): unhandled instruction: 0x10E40301
                 primary 4(0x4), secondary 769(0x301)
==2069== valgrind: Unrecognised instruction at address 0x4018ff0.
==2069== Your program just tried to execute an instruction that Valgrind
==2069== did not recognize.  There are two possible reasons for this.
==2069== 1. Your program has a bug and erroneously jumped to a non-code
==2069==    location.  If you are running Memcheck and you just saw a
==2069==    warning about a bad jump, it's probably your program's fault.
==2069== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2069==    i.e. it's Valgrind's fault.  If you think this is the case or
==2069==    you are not sure, please let us know and we'll try to fix it.
==2069== Either way, Valgrind will now raise a SIGILL signal which will
==2069== probably kill your program.
==2069==
==2069== Process terminating with default action of signal 4 (SIGILL)
==2069==  Illegal opcode at address 0x4018FF0
==2069==    at 0x4018FF0: memcpy (in /lib/ld-2.8.so)
==2069==    by 0x40021C3: _dl_start_final (in /lib/ld-2.8.so)
==2069==    by 0x4015F8B: _start (in /lib/ld-2.8.so)
==2069==
==2069== HEAP SUMMARY:
==2069==     in use at exit: 0 bytes in 0 blocks
==2069==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==2069==
==2069== All heap blocks were freed -- no leaks are possible
==2069==
==2069== For counts of detected and suppressed errors, rerun with: -v
==2069== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 2)

Could you please anybody suggest some clue to solve the above issue ?

Thank you,
Rajesh