Jason Molenda cb349ee19c When unwinding from the first frame, try to ask the remote debugserver ...

if this is a mapped/executable region of memory.  If it isn't, we've jumped
through a bad pointer and we know how to unwind the stack correctly based
on the ABI.  

Previously I had 0x0 special cased but if you jumped to 0x2 on x86_64 one
frame would be skipped because the unwinder would try using the x86_64 
ArchDefaultUnwindPlan which relied on the rbp.

Fixes <rdar://problem/10508291>

llvm-svn: 146477

2011-12-13 05:39:38 +00:00

..

testsuite

Spelling changes applied from lldb_spelling.diffs from Bruce Mitchener.

2011-01-08 20:28:42 +00:00

building-with-debug-llvm.txt

Instructions for building LLDB with a debug LLVM

2010-11-18 03:56:17 +00:00

code-signing.txt

Add a note.

2011-07-20 20:28:36 +00:00

lldb-for-gdb-users.txt

Add reference to ToT/examples/customization for more customization examples.

2011-10-12 19:20:04 +00:00

lldb-gdb-remote.txt

When unwinding from the first frame, try to ask the remote debugserver

2011-12-13 05:39:38 +00:00

try.me

just a test for commit access - ignore this

2011-06-29 04:18:11 +00:00