[Valgrind-users] Unrecognised instruction

[Joël K. <jo...@we...>]

Hi, I get this nice error message out of valgrind while starting or
using my application and I don't know why.

http://sf.net/p/ags

Please help.


--9862-- memcheck GC: 2827 nodes, 2355 survivors ( 83.3%)
--9862-- memcheck GC: 3997 new table size (stepup)
vex amd64->IR: unhandled instruction bytes: 0xC6 0xF8 0xFD 0xF 0xB7 0x6 0x66 0x85
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==9862== valgrind: Unrecognised instruction at address 0x34f3411390.
==9862==    at 0x34F3411390: __lll_trylock_elision (in /usr/lib64/libpthread-2.18.so)
==9862==    by 0x34F340A22B: pthread_mutex_trylock (in /usr/lib64/libpthread-2.18.so)
==9862==    by 0x4A1264: ags_gui_thread_do_gtk_iteration.60959 (ags_gui_thread.c:199)
==9862==    by 0x4A1539: ags_gui_thread_run (ags_gui_thread.c:251)
==9862==    by 0x34F70104C6: ??? (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==9862==    by 0x34F7029748: g_signal_emit_valist (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==9862==    by 0x34F702A3AE: g_signal_emit (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==9862==    by 0x49F625: ags_thread_run (ags_thread.c:1720)
==9862==    by 0x49F99E: ags_thread_loop (ags_thread.c:1643)
==9862==    by 0x34F3407F32: start_thread (in /usr/lib64/libpthread-2.18.so)
==9862==    by 0x34F2CF4EAC: clone (in /usr/lib64/libc-2.18.so)
==9862== Your program just tried to execute an instruction that Valgrind
==9862== did not recognise.  There are two possible reasons for this.
==9862== 1. Your program has a bug and erroneously jumped to a non-code
==9862==    location.  If you are running Memcheck and you just saw a
==9862==    warning about a bad jump, it's probably your program's fault.
==9862== 2. The instruction is legitimate but Valgrind doesn't handle it,
==9862==    i.e. it's Valgrind's fault.  If you think this is the case or
==9862==    you are not sure, please let us know and we'll try to fix it.
==9862== Either way, Valgrind will now raise a SIGILL signal which will
==9862== probably kill your program.
==9862== 
==9862== Process terminating with default action of signal 4 (SIGILL)
==9862==  Illegal opcode at address 0x34F3411390
==9862==    at 0x34F3411390: __lll_trylock_elision (in /usr/lib64/libpthread-2.18.so)
==9862==    by 0x34F340A22B: pthread_mutex_trylock (in /usr/lib64/libpthread-2.18.so)
==9862==    by 0x4A1264: ags_gui_thread_do_gtk_iteration.60959 (ags_gui_thread.c:199)
==9862==    by 0x4A1539: ags_gui_thread_run (ags_gui_thread.c:251)
==9862==    by 0x34F70104C6: ??? (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==9862==    by 0x34F7029748: g_signal_emit_valist (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==9862==    by 0x34F702A3AE: g_signal_emit (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==9862==    by 0x49F625: ags_thread_run (ags_thread.c:1720)
==9862==    by 0x49F99E: ags_thread_loop (ags_thread.c:1643)
==9862==    by 0x34F3407F32: start_thread (in /usr/lib64/libpthread-2.18.so)
==9862==    by 0x34F2CF4EAC: clone (in /usr/lib64/libc-2.18.so)
==9862== 
==9862== HEAP SUMMARY:
==9862==     in use at exit: 2,241,959 bytes in 29,002 blocks
==9862==   total heap usage: 91,386 allocs, 62,384 frees, 7,205,816 bytes allocated
==9862== 
==9862== Searching for pointers to 27,363 not-freed blocks
==9862== Checked 36,580,456 bytes
==9862== 
==9862== LEAK SUMMARY:
==9862==    definitely lost: 2,909 bytes in 41 blocks
==9862==    indirectly lost: 14,861 bytes in 633 blocks
==9862==      possibly lost: 66,719 bytes in 921 blocks
==9862==    still reachable: 1,865,142 bytes in 25,768 blocks
==9862==         suppressed: 0 bytes in 0 blocks
==9862== Rerun with --leak-check=full to see details of leaked memory
==9862== 
==9862== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
--9862-- 
--9862-- used_suppression:      2 glibc-2.5.x-on-SUSE-10.2-(PPC)-2a /usr/lib64/valgrind/default.supp:1286
==9862== 
==9862== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)