From a11668e87b9096c821ee9fd213e398e909b92965 Mon Sep 17 00:00:00 2001
From: Tatyana Krasnukha <tatyana@synopsys.com>
Date: Thu, 26 Sep 2019 10:57:11 +0000
Subject: Don't stop execution in batch mode when process stops with SIGINT or
 SIGSTOP

Summary: Usually, SIGINT and SIGSTOP don't imply a crash, e.g. SIGSTOP is sent on process launch and attach on some platforms.

Differential Revision: https://reviews.llvm.org/D67776

llvm-svn: 372961
---
 lldb/source/Commands/CommandObjectProcess.cpp | 1 -
 1 file changed, 1 deletion(-)

(limited to 'lldb/source/Commands/CommandObjectProcess.cpp')

diff --git a/lldb/source/Commands/CommandObjectProcess.cpp b/lldb/source/Commands/CommandObjectProcess.cpp
index b494740c62a..e5aa78afabb 100644
--- a/lldb/source/Commands/CommandObjectProcess.cpp
+++ b/lldb/source/Commands/CommandObjectProcess.cpp
@@ -429,7 +429,6 @@ protected:
         result.AppendMessage(stream.GetString());
         result.SetStatus(eReturnStatusSuccessFinishNoResult);
         result.SetDidChangeProcessState(true);
-        result.SetAbnormalStopWasExpected(true);
       } else {
         result.AppendError(
             "no error returned from Target::Attach, and target has no process");
-- 
cgit v1.2.3