Properly handle microdump processing, when the system_log file contains an incomplete microdump sec…

src/processor/microdump_processor_unittest.cc

Index: src/processor/microdump_processor_unittest.cc
diff --git a/src/processor/microdump_processor_unittest.cc b/src/processor/microdump_processor_unittest.cc
index 7dcfe44baa038c41b64a5e511c0b3070f8bbc437..a507b627f2a61acda9d858ce3cc2fed97d59ad18 100644
--- a/src/processor/microdump_processor_unittest.cc
+++ b/src/processor/microdump_processor_unittest.cc
@@ -212,6 +212,17 @@ TEST_F(MicrodumpProcessorTest, TestProcessX86) {
   // names.
 }
 
+TEST_F(MicrodumpProcessorTest, TestProcessMultiple) {
+  ProcessState state;
+  AnalyzeDump("microdump-multiple.dmp", false /* omit_symbols */,
+              6 /* expected_cpu_count */, &state);
+  ASSERT_EQ(133U, state.modules()->module_count());
+  ASSERT_EQ("arm", state.system_info()->cpu);
+  ASSERT_EQ("lge/p1_tmo_us/p1:6.0/MRA58K/1603210524c8d:user/release-keys",
+            state.system_info()->os_version);
+  ASSERT_EQ(2U, state.threads()->at(0)->frames()->size());
+}
+
 }  // namespace
 
 int main(int argc, char* argv[]) {