[LLVMdev] Why gdb can't determine stack of code run in JIT?

[Török Edwin]

On Sun, 17 Oct 2010 11:28:35 -0400
Reid Kleckner <reid.kleckner at gmail.com> wrote:

> I know you haven't been able to get the JIT gdb support to work on
> FreeBSD (right?), but this is exactly the problem that we ran into
> that it solves.
> 
> http://llvm.org/docs/DebuggingJITedCode.html
> 
> I don't know what heuristic gdb is trying to use to unwind the stack,
> but it doesn't work.  I asked a gdb developer about it two summers ago
> when I was working on this, but he seemed dismissive about teaching
> gdb how to get this right.

Doesn't LLVM already generate asynchronous unwind tables for exception
handling purposes? On x86-64 thats the only way to get a stacktrace
anyway since framepointers are omitted by default.
Won't unwinding the stack via async unwind tables work (or be made to
work) on x86-32 too?

Best regards,
--Edwin