Read Chrome build ID and store it in leak reports

chrome/browser/metrics/leak_detector/leak_detector_controller.cc

Index: chrome/browser/metrics/leak_detector/leak_detector_controller.cc
diff --git a/chrome/browser/metrics/leak_detector/leak_detector_controller.cc b/chrome/browser/metrics/leak_detector/leak_detector_controller.cc
index 68a01d44f83bc3f2e9a30b07b073c0b359d74589..165d6f66b9d5117c708bd910e5a45a0b24dde036 100644
--- a/chrome/browser/metrics/leak_detector/leak_detector_controller.cc
+++ b/chrome/browser/metrics/leak_detector/leak_detector_controller.cc
@@ -8,6 +8,7 @@
 
 #include "base/logging.h"
 #include "base/strings/string_number_conversions.h"
+#include "components/metrics/leak_detector/gnu_build_id_reader.h"
 #include "components/variations/variations_associated_data.h"
 #include "content/public/browser/browser_thread.h"
 
@@ -90,6 +91,11 @@ MemoryLeakReportProto::Params GetVariationParameters() {
 
 LeakDetectorController::LeakDetectorController()
     : params_(GetVariationParameters()) {
+  // Read the build ID once and store it.
+  bool build_id_read =
+      leak_detector::gnu_build_id_reader::ReadBuildID(&build_id_);
+  DCHECK(build_id_read);

[Simon Que, 2016/07/25 21:25:26]

Unit tests are failing this DCHECK because the unit_tests binary does not have a
build ID.

Perhaps we should just disregard the return value, and allow a binary not to
have a build ID. The |build_id_| vector would just be left empty.

+
   LeakDetector* detector = LeakDetector::GetInstance();
   detector->AddObserver(this);
 
@@ -138,6 +144,8 @@ void LeakDetectorController::StoreLeakReports(
     stored_reports_.push_back(report);
     stored_reports_.back().mutable_params()->CopyFrom(params_);
     stored_reports_.back().set_source_process(process_type);
+    stored_reports_.back().mutable_build_id()->assign(build_id_.begin(),
+                                                      build_id_.end());
   }
 }