From cc2139ec63c2d062b077c9c221917325c3f30f17 Mon Sep 17 00:00:00 2001 From: Laurent Pinchart Date: Fri, 21 May 2021 12:18:54 +0300 Subject: 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 Reviewed-by: Hirokazu Honda Reviewed-by: Paul Elder Reviewed-by: Kieran Bingham --- src/libcamera/log.cpp | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'src/libcamera/log.cpp') diff --git a/src/libcamera/log.cpp b/src/libcamera/log.cpp index 94175ab3..98595224 100644 --- a/src/libcamera/log.cpp +++ b/src/libcamera/log.cpp @@ -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 */ /** -- cgit v1.2.1