summaryrefslogtreecommitdiffstats
path: root/llvm/docs/DebuggingJITedCode.html
diff options
context:
space:
mode:
authorEric Christopher <echristo@apple.com>2010-06-18 22:33:17 +0000
committerEric Christopher <echristo@apple.com>2010-06-18 22:33:17 +0000
commit64ae6577ba44a429e38e4289d049af3267ecc82d (patch)
treedc55d5c385ef66076e94d1f715bb58ee2817023c /llvm/docs/DebuggingJITedCode.html
parent07f4fa819807ee9ee37fff10a5354942a1af9290 (diff)
downloadbcm5719-llvm-64ae6577ba44a429e38e4289d049af3267ecc82d.tar.gz
bcm5719-llvm-64ae6577ba44a429e38e4289d049af3267ecc82d.zip
Fix typo.
llvm-svn: 106335
Diffstat (limited to 'llvm/docs/DebuggingJITedCode.html')
-rw-r--r--llvm/docs/DebuggingJITedCode.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/docs/DebuggingJITedCode.html b/llvm/docs/DebuggingJITedCode.html
index 92570f454c9..adca01d88c4 100644
--- a/llvm/docs/DebuggingJITedCode.html
+++ b/llvm/docs/DebuggingJITedCode.html
@@ -28,7 +28,7 @@ no such file to look for.
<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
-compile with -fno-omit-framepointer for GCC and -fdisable-fp-elim for LLVM.
+compile with -fno-omit-frame-pointer for GCC and -fdisable-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
OpenPOWER on IntegriCloud