> vex mips->IR: unhandled instruction bytes: 0x0 0x0 0x0 0xE > ==3262== valgrind: Unrecognised instruction at address 0x490fc04. > ==3262== at 0x490FC04: ??? (in /lib/libstdc++.so.6.0.3) > ==3262== by 0x490FBC8: ??? (in /lib/libstdc++.so.6.0.3)
> We are using uclibc 0.9.28 running on Linux kernel 3.4.52. The MIPS > processor is a MIPS 24Kc and the GCC toolchain version is gcc 3.4.4 Thank you for a good report, including those details about the environment. To make it even better, which version of valgrind? ($ valgrind --version) valgrind-3.9.0 was released recently. Is your CPU running big-endian or little-endian? One way interprets ".byte 0,0,0,0xe" as a 'jal' instruction. For the other way, GNU gdb 6.8 does not recognize it, which may mean the instruction is an architectural extension or CPU-specific function: GNU gdb 6.8 (gdb) x/i 0 0x0 <_start>: jal 0x8000000 0x4 <_start+4>: 0xe (gdb) x/2x 0 0x0 <_start>: 0x0e000000 0x0000000e Your next step is to file a bug report so that the developers don't lose track of the problem. Go to https://bugs.kde.org/enter_bug.cgi?product=valgrind , then enter the same info there as you posted here. This will maximize the probability that valgrind developers will see and solve the problem. -- ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
