From 1ec7c15613028c75cf160a56bec0642a99109551 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Tue, 10 May 2022 14:12:57 +0200 Subject: Do LOG_MESSAGE_VERIFICATION in coverity runs This should be enough to get reports if we screw up anywhere, coverity does analysis of printf format strings. --- src/basic/log.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/basic/log.h') diff --git a/src/basic/log.h b/src/basic/log.h index b03ca3ef21..7b89c4df63 100644 --- a/src/basic/log.h +++ b/src/basic/log.h @@ -300,7 +300,7 @@ bool log_on_console(void) _pure_; /* Helper to wrap the main message in structured logging. The macro doesn't do much, * except to provide visual grouping of the format string and its arguments. */ -#if LOG_MESSAGE_VERIFICATION +#if LOG_MESSAGE_VERIFICATION || defined(__COVERITY__) /* Do a fake formatting of the message string to let the scanner verify the arguments * against the format message. */ # define LOG_MESSAGE(fmt, ...) "MESSAGE=%.0d" fmt, printf(fmt, ##__VA_ARGS__), ##__VA_ARGS__ -- cgit v1.2.3