[Valgrind-users] Illegal opcode when running Valgrind on ARM

[JoSH L. <kr...@gm...>]

Hello.  I'm running the latest version of Valgrind from the Subversion
tree, cross-compiled for ARM.

It compiled OK, and runs correctly on my ARM board, which is an Atmel
AT91SAM9260 (an ARM926).  I'm running the "arm-none-linux-gnueabi"
cross-compilation tools from CodeSourcery, version 2008q3.

All software compiled with this setup works on my ARM board, so I know
it's not a problem with my cross-compilation setup.

I had to change one thing in order to get it to compile: the
"configure" script complained that my setting of the --host option
wasn't a recognized architecture, because it tests for strings that
look like "armv7*".  So, I just changed "armv7*" to "arm*", to make it
a little more liberal in what it accepts, and it worked.

Valgrind runs on my ARM board, but unfortunately, upon encountering
the very first instruction of a "Hello World" program, it aborts the
program with SIGILL and prints the "Illegal opcode" error message.
The various summary counts are correct, and the help screen also works
just fine, so I know that it's not a problem starting up Valgrind
itself.  I tried "Hello World" again, compiled static (just to rule
out a problem with a library).  Running Valgrind on a known-good
program, such as /bin/ls, also produces the same failure.

Any idea on how I can troubleshoot this?  Unfortunately, the opcodes
that are supposedly illegal are not printed.  I attempted to add a
block to the error message handler, to print out the bytes at the
address that was given, but ended up evidently getting the wrong area
of memory instead (the bytes that appeared there did not match what
was in the ".text" segment of the file, as shown by "objdump").  Is
the ARM926's instruction set (ARMv5TEJ) supported?  I'm not trying to
use any exotic features of ARM, such as Thumb or NEON.

Thanks!

Josh Lehan