Jim Ingham a435d73349 Work around some odd instruction single-step behavior on macOS. ... We've seen some cases on macOS where you go to instruction single step (over a breakpoint), and single step returns but the instruction hasn't been executed (and the pc hasn't moved.) The ThreadPlanStepOverBreakpoint used to handle this case by accident, but the patches to handle two adjacent breakpoints broke that accident. This patch fixes the logic of ExplainsStop to explicitly handle the case where the pc didn't move. It also adds a WillPop that re-enables the breakpoint we were stepping over. We never want an unexpected path through the plan to fool us into not doing that. I have no idea how to make this bug happen. It is very inconsistent when it occurs IRL. We really need a full MockProcess Plugin before we can start to write tests for this sort of system hiccup. <rdar://problem/38505726> llvm-svn: 332922		2018-05-22 00:06:55 +00:00
..
LLDB.xcscheme	Update xcode project file to build new ppc64le files.	2017-11-17 01:55:50 +00:00
Run Testsuite.xcscheme	Xcode suggested enabling a "no common blocks" warning	2015-10-29 00:21:14 +00:00
darwin-debug.xcscheme	Update xcode project file to build new ppc64le files.	2017-11-17 01:55:50 +00:00
desktop.xcscheme	Work around some odd instruction single-step behavior on macOS.	2018-05-22 00:06:55 +00:00
launcherRootXPCService.xcscheme	Xcode suggested enabling a "no common blocks" warning	2015-10-29 00:21:14 +00:00
launcherXPCService.xcscheme	Xcode suggested enabling a "no common blocks" warning	2015-10-29 00:21:14 +00:00
lldb-gtest.xcscheme	Added real editline tests.	2015-10-30 02:54:52 +00:00
lldb-python-test-suite.xcscheme	remove xcshareddata exclusion from .gitignore; add desktop and lldb-python-testsuite shared schemes used by Xcode buildbot	2015-12-18 22:08:24 +00:00
lldb-tool.xcscheme	Add an "offset" option to "break set -n" and "break set -f -l".	2016-03-09 18:59:13 +00:00