Fix AOS logging when using non-EventLoop configuration
Fixed crash in aos::Logger when reading back a log that was made
by providing a different configuration to the Logger than was
used by the event loop.
Change event_loop_to_logged_channel_index_ to use
`std::optional<uint32_t>` instead of `int`. Channel indices
should be uint32_t. Changed to optional because the channel can
be missing from the configuration specified in the logger
Constructor.
Change-Id: I5203b390689cab27cd79ee35b029cfdd0f98dfd8
Signed-off-by: James Kuszmaul <james.kuszmaul@bluerivertech.com>
diff --git a/aos/events/logging/logfile_utils.cc b/aos/events/logging/logfile_utils.cc
index 0166b72..326fa6d 100644
--- a/aos/events/logging/logfile_utils.cc
+++ b/aos/events/logging/logfile_utils.cc
@@ -1824,6 +1824,7 @@
size_t monotonic_remote_boot = 0xffffff;
if (msg->monotonic_remote_time.has_value()) {
+ CHECK_LT(msg->channel_index, source_node_index_.size());
const Node *node = parts().config->nodes()->Get(
source_node_index_[msg->channel_index]);