|author||Laurent Pinchart <email@example.com>||2021-05-21 12:18:54 +0300|
|committer||Laurent Pinchart <firstname.lastname@example.org>||2021-05-22 02:56:25 +0300|
libcamera: log: Document LOG() restrictions
The LOG() macro uses the global Logger and LogCategory objects internally. This can result in crashes or other undefined behaviour when logging from destructors of global objects, as the Logger and/or the LogCategory instances may have been destroyed. This isn't ideal and should eventually be fixed. For the time being, document the restriction, and add a todo list item to fix the problem. Signed-off-by: Laurent Pinchart <email@example.com> Reviewed-by: Hirokazu Honda <firstname.lastname@example.org> Reviewed-by: Paul Elder <email@example.com> Reviewed-by: Kieran Bingham <firstname.lastname@example.org>
Diffstat (limited to 'src')
1 files changed, 6 insertions, 0 deletions
diff --git a/src/libcamera/log.cpp b/src/libcamera/log.cpp
index 94175ab3..98595224 100644
@@ -980,6 +980,12 @@ LogMessage _log(const LogCategory *category, LogSeverity severity,
* If the severity is set to Fatal, execution is aborted and the program
* terminates immediately after printing the message.
+ * \warning Logging from the destructor of a global object, either directly or
+ * indirectly, results in undefined behaviour.
+ * \todo Allow logging from destructors of global objects to the largest
+ * possible extent