Another typo.

llvm-svn: 106340
This commit is contained in:
Eric Christopher 2010-06-18 22:51:25 +00:00
parent c599143b45
commit b04dbfd059

View File

@ -28,7 +28,7 @@ no such file to look for.
<p>Depending on the architecture, this can impact the debugging experience in <p>Depending on the architecture, this can impact the debugging experience in
different ways. For example, on most 32-bit x86 architectures, you can simply 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 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. 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 However, on Linux x86_64 in particular, GDB relies on the DWARF CFA debug