search for: 0x464d10

Displaying 1 result from an estimated 1 matches for "0x464d10".

Did you mean: 0.46410
2009 Feb 26
1
[LLVMdev] Problem with x86_64 JIT from a .so on Linux (LLVM 2.4)
...2307)] 0x00002acc00464d10 in ?? () (gdb) bt #0 0x00002acc00464d10 in ?? () #1 0x00002acc1869f026 in ?? () #2 0x000000000074eb10 in ?? () #3 0x000000000074eb10 in ?? () #4 0x0000000000000000 in ?? () This is the jitted function: the last call refers 0x2acc00464d10, while the correct address is 0x464d10 (gdb) disass 0x00002acc1869f010 0x00002acc1869f026 Dump of assembler code from 0x2acc1869f010 to 0x2acc1869f026: 0x00002acc1869f010: push %r14 0x00002acc1869f012: push %rbx 0x00002acc1869f013: sub $0x8,%rsp 0x00002acc1869f017: mov $0x7f0ed0,%edi 0x00002acc1869f01c: cal...