forked from OSchip/llvm-project
c3c721222d
Summary: When a call instruction is the last instruction in a function, the backtrace PC will point past the end of the function. We already had special code to handle that, but we did not handle the case where the PC ends up outside of the bounds of the module containing the function, which is a situation that occured in TestNoreturnUnwind on android for some arch/compiler combinations. I fix this by adding an argument to Address resolution code which states that we are ok with addresses pointing to the end of a module/section to resolve to that module/section. I create a reproducible test case for this situation by hand-crafting an executable which has a noreturn function at the end of a module. Reviewers: jasonmolenda, jingham Subscribers: lldb-commits Differential Revision: https://reviews.llvm.org/D32022 llvm-svn: 304976 |
||
|---|---|---|
| .. | ||
| API | ||
| Breakpoint | ||
| Core | ||
| DataFormatters | ||
| Expression | ||
| Host | ||
| Initialization | ||
| Interpreter | ||
| Symbol | ||
| Target | ||
| Utility | ||
| lldb-defines.h | ||
| lldb-enumerations.h | ||
| lldb-forward.h | ||
| lldb-private-defines.h | ||
| lldb-private-enumerations.h | ||
| lldb-private-forward.h | ||
| lldb-private-interfaces.h | ||
| lldb-private-types.h | ||
| lldb-private.h | ||
| lldb-public.h | ||
| lldb-types.h | ||
| lldb-versioning.h | ||