> ==5290== Process terminating with default action of signal 4 (SIGILL) > ==5290== Illegal opcode at address 0x3808AE70 > ==5290== at 0x4000E50: _start (in /lib/ld-uClibc-0.9.32.1.so)
> # cat /proc/cpuinfo > Processor : ARMv7 Processor rev 1 (v7l) > processor : 0 > BogoMIPS : 1987.37 > processor : 1 > BogoMIPS : 1993.93 > Features : swp half thumb fastmult edsp tls This smells like valgrind was built (compiled) for some other ARM architecture, but installed on this box. Or, it could be a bug the code which valgrind uses to determine the current CPU architecture. Find out what instruction (the four bytes) is at 0x3808AE70, and tell is in hex and disassembled (use gdb). That address is inside one of the valgrind tools itself. On x86_64 it would be /usr/lib64/valgrind/memcheck-amd64-linux so look for /usr/lib/valgrind/memcheck-arm*-linux or similar. Then run gdb on that file, and say: x/x 0x3808AE70 x/i 0x3808AE70 q -- ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
