The vDbgPrintEx[1] sends a message to the Windows kernel debugger, if
"DBG_PRINT" is defined. The va_start and va_end macros[2] fetch
function's optional arguments. They only move the list pointer around,
so va_start after va_end is safe.
I don't see a problem with this and it sounds useful, so it
Signed-off-by: Alon Bar-Lev
---
src/error.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/src/error.c b/src/error.c
index 5b25f48..0541bc3 100755
--- a/src/error.c
+++ b/src/error.c
@@ -81,6 +81,11 @@ MyDebugPrint (const unsigned char* format, ...)
NT
