Actually manage memory in the old-style AOS logging
LeakSanitizer should be happy with it now. It's also still just as
thread-safe.
Change-Id: Id09a0349657cf4f719267b053f0ea3d8ec366256
diff --git a/aos/vision/debug/debug_framework.cc b/aos/vision/debug/debug_framework.cc
index 47e0856..0b0d2c7 100644
--- a/aos/vision/debug/debug_framework.cc
+++ b/aos/vision/debug/debug_framework.cc
@@ -62,9 +62,8 @@
}
// Pass along the set exposure so that users can acceess it.
- filter->InstallSetExposure([this](uint32_t abs_exp) {
- this->SetExposure(abs_exp);
- });
+ filter->InstallSetExposure(
+ [this](uint32_t abs_exp) { this->SetExposure(abs_exp); });
}
// This the first stage in the pipeline that takes
@@ -151,8 +150,6 @@
void DebugFrameworkMain(int argc, char **argv, FilterHarness *filter,
CameraParams camera_params) {
::aos::logging::Init();
- ::aos::logging::SetImplementation(
- new ::aos::logging::StreamLogImplementation(stdout));
gtk_init(&argc, &argv);