momesana
9th November 2006, 00:00
When I run valgrind on Qt apps, it always reports this error and exits:
unhandled opc_aux = 0x 1
first_opcode == 0xDD
vex x86->IR: unhandled instruction bytes: 0xDD 0xC 0x24 0x8B
==19005== valgrind: Unrecognised instruction at address 0x479851D.
==19005== Your program just tried to execute an instruction that Valgrind
==19005== did not recognise. There are two possible reasons for this.
==19005== 1. Your program has a bug and erroneously jumped to a non-code
==19005== location. If you are running Memcheck and you just saw a
==19005== warning about a bad jump, it's probably your program's fault.
==19005== 2. The instruction is legitimate but Valgrind doesn't handle it,
==19005== i.e. it's Valgrind's fault. If you think this is the case or
==19005== you are not sure, please let us know and we'll try to fix it.
==19005== Either way, Valgrind will now raise a SIGILL signal which will
==19005== probably kill your program.
==19005==
==19005== Process terminating with default action of signal 4 (SIGILL)
==19005== Illegal opcode at address 0x479851D
==19005== at 0x479851D: (within /usr/lib/libfontconfig.so.1.0.4)
==19005== by 0x3801707F: (within /usr/lib/valgrind/x86-linux/memcheck)
==19005== by 0x1000: ???
Any clue?
Thanx in advance
momesana
unhandled opc_aux = 0x 1
first_opcode == 0xDD
vex x86->IR: unhandled instruction bytes: 0xDD 0xC 0x24 0x8B
==19005== valgrind: Unrecognised instruction at address 0x479851D.
==19005== Your program just tried to execute an instruction that Valgrind
==19005== did not recognise. There are two possible reasons for this.
==19005== 1. Your program has a bug and erroneously jumped to a non-code
==19005== location. If you are running Memcheck and you just saw a
==19005== warning about a bad jump, it's probably your program's fault.
==19005== 2. The instruction is legitimate but Valgrind doesn't handle it,
==19005== i.e. it's Valgrind's fault. If you think this is the case or
==19005== you are not sure, please let us know and we'll try to fix it.
==19005== Either way, Valgrind will now raise a SIGILL signal which will
==19005== probably kill your program.
==19005==
==19005== Process terminating with default action of signal 4 (SIGILL)
==19005== Illegal opcode at address 0x479851D
==19005== at 0x479851D: (within /usr/lib/libfontconfig.so.1.0.4)
==19005== by 0x3801707F: (within /usr/lib/valgrind/x86-linux/memcheck)
==19005== by 0x1000: ???
Any clue?
Thanx in advance
momesana