I found that the restgpr symbols were being included because I was
configuring crosstool-NG with CT_CC_GCC_ENABLE_TARGET_OPTSPACE, which
compiles gcc libs with "-Os". I rebuilt the toolchain without this
option and Valgrind no longer complains about missing symbols or
unrecognized instructions. The
Those happen, don't take it personally. They used to be real common
in ARM. Sounds like you hit a code that's not covered. Not that I'm
one that can add it.
See the "==466== Your program just tried to execute an instruction that Valgrind
==466== did not recognise." section of the error message
I'm trying to use Valgrind on an embedded PowerPC system but I'm
getting the following errors:
./testprog: symbol lookup error:
/usr/local/lib/valgrind/vgpreload_memcheck-ppc32-linux.so: undefined
symbol: _restgpr_30_x
disInstr(ppc): unhandled instruction: 0x0
primary 0(0x0), seco
