aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectProcess.cpp
diff options
context:
space:
mode:
authorJim Ingham <jingham@apple.com>2016-01-08 00:20:47 +0000
committerJim Ingham <jingham@apple.com>2016-01-08 00:20:47 +0000
commit962260c852c945d529ac32dced2c456b6f58097f (patch)
tree17a0701cf8db9fcf8b896811e530898378d1ea0f /lldb/source/Commands/CommandObjectProcess.cpp
parent3a7c2f6f44627ab325a0af706760e53d3f491c76 (diff)
downloadllvm-962260c852c945d529ac32dced2c456b6f58097f.zip
llvm-962260c852c945d529ac32dced2c456b6f58097f.tar.gz
llvm-962260c852c945d529ac32dced2c456b6f58097f.tar.bz2
Fix a glitch in the Driver's batch mode when used with "attach".
Batch mode is supposed to stop execution and return control to the user when an exceptional stop occurs (crash, signal or instrumentation). But attach always stops with a SIGSTOP on OSX (maybe on Linux too?) which would short circuit the rest of the commands given. This change allows a command result object to indicate that it expected to leave the process stopped with an exceptional stop reason, and it is okay for batch mode to keep going. <rdar://problem/22243143> llvm-svn: 257120
Diffstat (limited to 'lldb/source/Commands/CommandObjectProcess.cpp')
-rw-r--r--lldb/source/Commands/CommandObjectProcess.cpp1
1 files changed, 1 insertions, 0 deletions
diff --git a/lldb/source/Commands/CommandObjectProcess.cpp b/lldb/source/Commands/CommandObjectProcess.cpp
index b7f894f..a85ea17 100644
--- a/lldb/source/Commands/CommandObjectProcess.cpp
+++ b/lldb/source/Commands/CommandObjectProcess.cpp
@@ -550,6 +550,7 @@ protected:
result.AppendMessage(stream.GetData());
result.SetStatus (eReturnStatusSuccessFinishNoResult);
result.SetDidChangeProcessState (true);
+ result.SetAbnormalStopWasExpected(true);
}
else
{