Mutex callbacks vector in timer

This is theoretical, because I never called addCallback() after having started the timer.

Mutex callbacks vector in timer
This is theoretical, because I never called addCallback() after having started the timer.
Wiebe Cazemier
1 parent b18af18a
Showing 2 changed files with 6 additions and 0 deletions
timer.cpp
timer.h
@@ -82,6 +82,8 @@ void Timer::addCallback(std::function&lt;void ()&gt; f, uint64_t interval_ms, const st
 {
     logger->logf(LOG_DEBUG, "Adding event '%s' to the timer with an interval of %ld ms.", name.c_str(), interval_ms);
  
+    std::lock_guard<std::mutex> locker(this->callbacksMutex);
+
     CallbackEntry c;
     c.f = f;
     c.interval = interval_ms;
@@ -137,6 +139,9 @@ void Timer::process()
         }
  
         logger->logf(LOG_DEBUG, "Calling timed event '%s'.", callbacks.front().name.c_str());
+
+        std::lock_guard<std::mutex> locker(this->callbacksMutex);
+
         CallbackEntry &c = callbacks.front();
         c.updateExectedAt();
         c.f();
@@ -50,6 +50,7 @@ class Timer
     int running = false;
     Logger *logger = Logger::getInstance();
     std::vector<CallbackEntry> callbacks;
+    std::mutex callbacksMutex;
  
     void sortAndSetSleeptimeTillNext();
     void process();