From 69a462ef710b01ee8781dbf814b7088b302d506a Mon Sep 17 00:00:00 2001 From: Eric Christopher Date: Fri, 18 Jun 2010 22:51:25 +0000 Subject: [PATCH] Another typo. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@106340 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/DebuggingJITedCode.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/DebuggingJITedCode.html b/docs/DebuggingJITedCode.html index adca01d88c4..83acbe439bb 100644 --- a/docs/DebuggingJITedCode.html +++ b/docs/DebuggingJITedCode.html @@ -28,7 +28,7 @@ no such file to look for.

Depending on the architecture, this can impact the debugging experience in different ways. For example, on most 32-bit x86 architectures, you can simply -compile with -fno-omit-frame-pointer for GCC and -fdisable-fp-elim for LLVM. +compile with -fno-omit-frame-pointer for GCC and -disable-fp-elim for LLVM. When GDB creates a backtrace, it can properly unwind the stack, but the stack frames owned by JITed code have ??'s instead of the appropriate symbol name. However, on Linux x86_64 in particular, GDB relies on the DWARF CFA debug