qapi: Don't pass NULL to printf in string input visitor
authorEric Blake <eblake@redhat.com>
Thu, 28 Apr 2016 21:45:28 +0000 (15:45 -0600)
committerMarkus Armbruster <armbru@redhat.com>
Fri, 29 Apr 2016 09:11:36 +0000 (11:11 +0200)
Make sure the error message for visit_type_uint64() gracefully
handles a NULL 'name' when called from the top level or a list
context, as not all the world behaves like glibc in allowing
NULL through a printf-family %s.

Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <1461879932-9020-21-git-send-email-eblake@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
qapi/string-input-visitor.c

index ab129536e47bcef52522d6d008a4b69e548287d8..5ea2d77b5ad95f9645640d706db4cc47e9403cd4 100644 (file)
@@ -222,7 +222,7 @@ static void parse_type_int64(Visitor *v, const char *name, int64_t *obj,
     return;
 
 error:
-    error_setg(errp, QERR_INVALID_PARAMETER_VALUE, name,
+    error_setg(errp, QERR_INVALID_PARAMETER_VALUE, name ? name : "null",
                "an int64 value or range");
 }