summaryrefslogtreecommitdiff
path: root/vl.c
diff options
context:
space:
mode:
authorKevin Wolf <kwolf@redhat.com>2009-05-19 18:51:34 +0200
committerAnthony Liguori <aliguori@us.ibm.com>2009-05-27 09:44:51 -0500
commit8cf07dcbe7691dbe4f47563058659dba6ef66b05 (patch)
tree2f0317bd09c6c8bfb565028a06b1b11d961f9d75 /vl.c
parent7696d1ecd0fe4805b630161d276a169c01f80e91 (diff)
downloadqemu-8cf07dcbe7691dbe4f47563058659dba6ef66b05.tar.gz
Fix output of uninitialized strings
Commit ffad4116b96e29e0fbe892806f97c0a6c903d30d removed the "scratch buffer" from check_params, but didn't care for the error messages which actually included this string to tell the user which option was wrong. Now this string is uninitialized, so this patch removes it from the message. This means that the user is only told the whole parameter string and has to pick the wrong option by himself as the callers of check_params can't know this value any more. An alternative approach would be to revert that commit and do whatever is needed to fix the original problem without changing check_params. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'vl.c')
-rw-r--r--vl.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/vl.c b/vl.c
index 2c1f0e0bd2..b1216c0183 100644
--- a/vl.c
+++ b/vl.c
@@ -2227,8 +2227,7 @@ int drive_init(struct drive_opt *arg, int snapshot, void *opaque)
NULL };
if (check_params(params, str) < 0) {
- fprintf(stderr, "qemu: unknown parameter '%s' in '%s'\n",
- buf, str);
+ fprintf(stderr, "qemu: unknown parameter in '%s'\n", str);
return -1;
}