On Wed, 2013-11-27 at 17:05 +0100, Benjamin Schindler wrote:
> Hmm
> Unfortunatelly, I moved from Vienna to Zurich now and I don't have
> access to the machine which showed this behavior. I just tried to
> reproduce it on my gentoo box but there, it just worked fine. So I think
> it has likely s
> 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
Hmm
Unfortunatelly, I moved from Vienna to Zurich now and I don't have
access to the machine which showed this behavior. I just tried to
reproduce it on my gentoo box but there, it just worked fine. So I think
it has likely something to do with dependent libs. After all,
backporting an unstable
Hi,
First off thanks for the amazing work on valgrind and bringing this
excellent tool to mips :)
I've just found out that the mips port was completed a while ago and have
tried to use it on our embedded devices. It works fine on basic Linux
commands like 'ls' and 'pwd', but as soon as I us
