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/dump_rtprio.cc b/aos/dump_rtprio.cc
index 5d9a0b4..5f4397f 100644
--- a/aos/dump_rtprio.cc
+++ b/aos/dump_rtprio.cc
@@ -7,17 +7,17 @@
// exe,name,cpumask,policy,nice,priority,tid,pid,ppid,sid,cpu
#include <sched.h>
-#include <stdlib.h>
-#include <stdio.h>
#include <stdint.h>
-#include <sys/time.h>
+#include <stdio.h>
+#include <stdlib.h>
#include <sys/resource.h>
+#include <sys/time.h>
#include <unistd.h>
#include <string>
-#include "aos/logging/logging.h"
#include "aos/logging/implementations.h"
+#include "aos/logging/logging.h"
#include "aos/time/time.h"
namespace {
@@ -248,8 +248,6 @@
int main() {
::aos::logging::Init();
- ::aos::logging::SetImplementation(
- new ::aos::logging::StreamLogImplementation(stdout));
const int pid_max = find_pid_max();
const cpu_set_t all_cpus = find_all_cpus();