6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-05-28 00:40:54 +00:00
Code Issues Projects Releases Wiki Activity

Fix typo.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@106335 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Eric Christopher 2010-06-18 22:33:17 +00:00
parent 0465bcffbb
commit 6492a3561a
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/DebuggingJITedCode.html
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-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 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