ProcessMinidump: Suppress reporting stop for signal '0'
authorJoseph Tremoulet <jotrem@microsoft.com>
Fri, 18 Oct 2019 15:02:16 +0000 (15:02 +0000)
committerJoseph Tremoulet <jotrem@microsoft.com>
Fri, 18 Oct 2019 15:02:16 +0000 (15:02 +0000)
commit77460d3888c56a6ed8184783388ed109590ee199
tree1b7edabdf565146724182dc281b0f19974aadfbf
parentd094d97d02232f3c7c5b3b792760cedb5ccac25b
ProcessMinidump: Suppress reporting stop for signal '0'

Summary:
The minidump exception stream can report an exception record with
signal 0.  If we try to create a stop reason with signal zero, processing
of the stop event won't find anything, and the debugger will hang.
So, simply early-out of RefreshStateAfterStop in this case.

Also set the UnixSignals object in DoLoadCore as is done for
ProcessElfCore.

Reviewers: labath, clayborg, jfb

Reviewed By: labath, clayborg

Subscribers: dexonsmith, lldb-commits

Tags: #lldb

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

llvm-svn: 375244
lldb/packages/Python/lldbsuite/test/functionalities/postmortem/minidump-new/TestMiniDumpNew.py
lldb/packages/Python/lldbsuite/test/functionalities/postmortem/minidump-new/linux-x86_64_null_signal.yaml [new file with mode: 0644]
lldb/source/Plugins/Process/minidump/ProcessMinidump.cpp