Those unhandled instruction bytes might be a valgrind bug (actually, it has been), but your version doesnt look like the one reported there.
It would probably help to know more about this, it might be a JIT Bug.
Which game (or any game, if no specific one does this), and probably a memory image of the process at the time when valgrind throws this (piped thru objdump perhaps, filtered to the reported bytes).
I'm not so sure that this is the complete context where valgrind dies:
It would probably help to know more about this, it might be a JIT Bug.
Which game (or any game, if no specific one does this), and probably a memory image of the process at the time when valgrind throws this (piped thru objdump perhaps, filtered to the reported bytes).
I'm not so sure that this is the complete context where valgrind dies:
Code:
D:\_dev>udcli -x
66 f 29 c6 66 f
0000000000000000 660f29c6 movapd xmm6, xmm0