commit a8faf287507a7ee8ab1acbcd05c716d3a9adb1f2
author Austin Schuh <austin.linux@gmail.com> Sun Mar 08 14:49:53 2020 -0700
committer Austin Schuh <austin.linux@gmail.com> Sun Mar 08 14:52:38 2020 -0700
tree 07e0fa1bcec7a0135528422fd8a1c467b5f19350
parent dd9ce3747538db778505632a892bfde582d9327d

Core dump on SCHED_OTHER

This was happening on the RT scheduler and causing significant problems
when a process would crash.

Change-Id: Idec897f43daaf835a601c8a77dfe7f9bfafd62da

third_party/google-glog/src/logging.cc

diff --git a/third_party/google-glog/src/logging.cc b/third_party/google-glog/src/logging.cc
index ad4047d..2bfce3d 100644
--- a/third_party/google-glog/src/logging.cc
+++ b/third_party/google-glog/src/logging.cc
@@ -1459,6 +1459,13 @@
   // someone else can use them (as long as they flush afterwards)
   if (data_->severity_ == GLOG_FATAL && exit_on_dfatal) {
     if (data_->first_fatal_) {
+      {
+        // Put this back on SCHED_OTHER by default.
+        struct sched_param param;
+        param.sched_priority = 0;
+        sched_setscheduler(0, SCHED_OTHER, &param);
+      }
+
       // Store crash information so that it is accessible from within signal
       // handlers that may be invoked later.
       RecordCrashReason(&crash_reason);