From 71515ba190e90e0250b9de23b7ba871c1dd44f09 Mon Sep 17 00:00:00 2001 From: Andrew Kroeger Date: Fri, 12 Jun 2009 13:01:41 +0200 Subject: s4: Call va_end() after all va_start()/va_copy() calls. This corrects the issues reaised in bug #6129, and some others that were not originally identified. It also accounts for some code that was in the original bug report but appears to have since been made common between S3 and S4. Thanks to Erik Hovland for the original bug report. --- source4/lib/ldb/ldb_sqlite3/ldb_sqlite3.c | 1 + 1 file changed, 1 insertion(+) (limited to 'source4/lib/ldb') diff --git a/source4/lib/ldb/ldb_sqlite3/ldb_sqlite3.c b/source4/lib/ldb/ldb_sqlite3/ldb_sqlite3.c index 8acbac4cc3..d0573d389e 100644 --- a/source4/lib/ldb/ldb_sqlite3/ldb_sqlite3.c +++ b/source4/lib/ldb/ldb_sqlite3/ldb_sqlite3.c @@ -485,6 +485,7 @@ query_int(const struct lsqlite3_private * lsqlite3, /* Format the query */ if ((p = sqlite3_vmprintf(pSql, args)) == NULL) { + va_end(args); return SQLITE_NOMEM; } -- cgit