Unhandled instruction on mips, only on multi-threaded programs. 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 use a multi-threaded program (one of our own) I get an unhandled instruction error that looks like this: 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) .... ==3262== Process terminating with default action of signal 4 (SIGILL): dumping core ==3262== Illegal opcode at address 0x490FC04 ==3262== at 0x490FC04: ??? (in /lib/libstdc++.so.6.0.3) ==3262== by 0x490FBC8: ??? (in /lib/libstdc++.so.6.0.3) I built and configured valgrind with the following configure line to match our the options we use to build for mips: ./configure --prefix=<my-valgrind-install-directory> CFLAGS="-mips32r2 -mtune=24kec -mabi=32 -mlong-calls" --with-pagesize=4 --host-mips-linux I also patched the source to disable large file support to match our environment - http://git.buildroot.net/buildroot/plain/package/valgrind/valgrind- largefile.patch We are using uclibc 0.9.28 running on Linux kernel 3.4.52. The MIPS processor is a MIPS 24Kc, we are running big endian and the GCC toolchain version is gcc 3.4.4. The version of valgrind is 3.9.0.
There is a suggestion from a colleague that there may be an issue to do with Native POSIX Linux Thread, support for which does not come into uClibc until 0.9.32 (we're running 0.9.28) but I have no experience in this area.
>> vex mips->IR: unhandled instruction bytes: 0x0 0x0 0x0 0xE This means that the Valgrind is trying to execute xori instruction. This instruction is supported in Valgrind. Can you try to compile your V and your program with the newer compiler? Can you create a small reproducible program, compile it statically and attach the binary here so I can try it?
Is this problem still valid?
Yes it is. I'm in the process of creating an example program - apologies for the delay, I'll provide it as soon as I can.
(In reply to Julian from comment #4) > Yes it is. I'm in the process of creating an example program - apologies for > the delay, I'll provide it as soon as I can. Any update here?
Since there are no updates, I would close this issue.
Created attachment 88557 [details] attachment-4252-0.html Hi Petar, I'm sorry that there haven't been any updates, I haven't had a chance to follow this up with changing priorities at work. As far as I am aware it is still an issue for us but I understand if you want to close the issue. When I have some dedicated time in the future I can raise a new issue with all the information previously requested and hopefully with a more detailed analysis. Julian On 4 September 2014 02:22, Petar Jovanovic <mips32r2@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=328147 > > --- Comment #6 from Petar Jovanovic <mips32r2@gmail.com> --- > Since there are no updates, I would close this issue. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. >
Changed status to 'waiting for info'.
Any update here? Otherwise, the issue will be closed.
No updates or new info for 4 years. Closing it.