[Bug 23694] New: continue after SIGSEGV behaves strangely on android

Bug ID 23694
Summary continue after SIGSEGV behaves strangely on android
Product lldb
Version unspecified
Hardware PC
OS Linux
Status NEW
Severity normal
Priority P
Component All Bugs
Assignee labath@google.com
Reporter labath@google.com
CC lldb-dev@cs.uiuc.edu
Classification Unclassified

Android applications have a custom SEGV handler installed by default. When
continuing an application which has experienced a segfault, this handler
misbehaves and we end up receiving a SIGILL. We need to investigate why this
happens and what can be done about that.

labath@google.com changed bug 23694

What | Removed | Added |

  • | - | - |
    Status | NEW | RESOLVED |
    Resolution | — | FIXED |

Comment # 2 on bug 23694 from labath@google.com

Fixed. The problem was LLDB was setting a rogue breakpoint, which was
corrupting the inferior state.