aboutsummaryrefslogtreecommitdiff
path: root/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
commit6492a3561a96bbb280fdffc507b26ba9966f84a6 (patch)
tree4ac8d655c1e9ba73c2e08c6b73ef745402d28b16 /docs/DebuggingJITedCode.html
parent0465bcffbbffb5ff5f420787b4350cb8abb196f7 (diff)
Fix typo.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@106335 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/DebuggingJITedCode.html')
-rw-r--r--docs/DebuggingJITedCode.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/DebuggingJITedCode.html b/docs/DebuggingJITedCode.html
index 92570f454c..adca01d88c 100644
--- a/docs/DebuggingJITedCode.html
+++ b/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