|
From: Tom H. <to...@co...> - 2011-03-13 15:52:12
|
On 13/03/11 14:29, Paulo César Pereira de Andrade wrote: > I just switched development of my language, and its jit generation > based on gnu lightning on a x86_64 computer, and this happens > when running jit generated code under valgrind. > > (other valgrind messages about bug report, etc) It would have been helpful if you had included them... As it is you have cut off some information that may have been important. I assume that among them was the text which you have included as the subject of this message? > ==16208== Process terminating with default action of signal 4 (SIGILL) > ==16208== Illegal opcode at address 0x9F14FD8 > ==16208== at 0x9F14FD8: ??? > ==16208== > ==16208== ---- Attach to debugger ? --- [Return/N/n/Y/y/C/c] ---- y > > (gdb) x/20i 0x0000000009f14fd8-20 > 0x9f14fc4: xor %rax,%rax > 0x9f14fc7: rex.WB callq *%r13 > 0x9f14fca: nopw 0x0(%rax,%rax,1) > 0x9f14fd0: mov 0x20(%rbx),%r10 > 0x9f14fd4: mov -0x28(%r10),%r10 > => 0x9f14fd8: movslq 0x24(%r10),%r13d > 0x9f14fdc: mov 0x28(%rbx),%r10 > 0x9f14fe0: lea 0x18(%r10),%rax > 0x9f14fe4: mov %rax,0x28(%rbx) > 0x9f14fe8: movabs $0x1,%rax > 0x9f14ff2: mov %eax,(%r10) > 0x9f14ff5: mov %r13,0x8(%r10) > > (gdb) x/4x 0x9f14fd8 > 0x9f14fd8: 0x45 0x63 0x6a 0x24 That instruction should be handled by valgrind, but then you are looking at the output of valgrind there anyway, not the input, so it doesn't really tell us much. If you are getting an "unhandled instruction bytes" message from valgrind then you have almost certainly found a bug in valgrind and you should report it in the bug tracker. Make sure you include all the detail from at least that message onwards. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |