Jason Molenda 60f0bd4944 Add a new capability to RegisterContextLLDB: To recognize when the ... Full UnwindPlan is trying to do an impossible unwind; in that case invalidate the Full UnwindPlan and replace it with the architecture default unwind plan. This is a scenario that happens occasionally with arm unwinds in particular; the instruction analysis based full unwindplan can mis-parse the functions and the stack walk stops prematurely. Now we can do a simpleminded frame-chain walk to find the caller frame and continue the unwind. It's not ideal but given the complicated nature of analyzing the arm functions, and the lack of eh_frame information on iOS, it is a distinct improvement and fixes some long-standing problems with the unwinder on that platform. This is fixing <rdar://problem/12091421>. I may re-use this invalidate feature in the future if I can identify other cases where the full unwindplan's unwind information is clearly incorrect. This checkin also includes some cleanup for the volatile register definition in the arm ABI plugin for <rdar://problem/10652166> although work remains to be done for that bug. llvm-svn: 166757		2012-10-26 06:08:58 +00:00
..
InstEmulation	Change how the UnwindAssemblyInstEmulation class tracks the setup of	2012-10-23 03:08:31 +00:00
x86	Add a new capability to RegisterContextLLDB: To recognize when the	2012-10-26 06:08:58 +00:00