Don't set a software stepping breakpoint at 0 on arm or mips.
authorPavel Labath <labath@google.com>
Wed, 26 Oct 2016 11:13:56 +0000 (11:13 +0000)
committerPavel Labath <labath@google.com>
Wed, 26 Oct 2016 11:13:56 +0000 (11:13 +0000)
commit42eb6908e035c0b8160591c680007936ec306400
tree19bdf1269aa7e2be921d278b94fe6800e534c906
parentb380b24e6edc83030ea6bcc815763b77cbbf9a75
Don't set a software stepping breakpoint at 0 on arm or mips.

Summary:
Check whether the setting the breakpoint failed during instruction emulation. If
it did, the next pc is likely in unmapped memory, and the inferior will crash
anyway after the next instruction. Do not return an error in this case, but just
continue stepping.
Reenabled the crash during step test for android/linux.

Reviewers: labath

Subscribers: aemerson, rengolin, tberghammer, danalbert, srhines, lldb-commits

Differential Revision: https://reviews.llvm.org/D25926
Author: Jason Majors <jmajors@google.com>

llvm-svn: 285187
lldb/packages/Python/lldbsuite/test/functionalities/thread/crash_during_step/TestCrashDuringStep.py
lldb/source/Plugins/Process/Linux/NativeProcessLinux.cpp