Displaying 1 result from an estimated 1 matches for "1012806".
Did you mean:
101206
2010 Oct 16
5
[LLVMdev] Why gdb can't determine stack of code run in JIT?
I run some code in JIT on x86-64 architecture.
Even though llvm::NoFramePointerElim is set to true, I still see weird
stack in gdb, see below.
800b485a4 is the current rip register where gdb stopped. Then many
others values aren't valid. Then there is value that looks ok again.
Why gdb can't determine stack?
Yuri
-- stack --
#0 0x0000000800b485a4 in ?? ()
#1 0x000000000000005f in