From 4c9f506b2b4ef4edbb1432f07e82da3ece0ed17b Mon Sep 17 00:00:00 2001 From: Bryan Green Date: Mon, 13 Oct 2025 09:56:06 -0500 Subject: [PATCH] Fix incorrect fprintf usage in log_error FRONTEND path The FRONTEND branch of log_error() was calling fprintf() with a va_list argument, but fprintf() expects individual arguments. This should use vfprintf() instead to properly handle the va_list. While this code path may not be currently compiled in practice, it would fail to compile or crash at runtime if FRONTEND were ever defined for files containing this function. --- src/port/win32security.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/port/win32security.c b/src/port/win32security.c index a46b82dd04..c531a4fc05 100644 --- a/src/port/win32security.c +++ b/src/port/win32security.c @@ -33,7 +33,7 @@ log_error(const char *fmt,...) #ifndef FRONTEND write_stderr(fmt, ap); #else - fprintf(stderr, fmt, ap); + vfprintf(stderr, fmt, ap); #endif va_end(ap); } -- 2.49.0