From: Paolo Bonzini <pbonz...@redhat.com> If expected_args is 0, qtest frees the argument vector and then returns it nevertheless. Coverity complains; in practice this is not an issue because expected_args == 0 means that the caller is not interested in the argument vector, but it would be a potential problem if somebody wanted to add commands with optional arguments to qtest.
Suggested-by: Kamil Dudka <kdu...@redhat.com> Signed-off-by: Paolo Bonzini <pbonz...@redhat.com> Message-Id: <20201120073149.99079-1-pbonz...@redhat.com> Reviewed-by: Thomas Huth <th...@redhat.com> Reviewed-by: Markus Armbruster <arm...@redhat.com> Signed-off-by: Thomas Huth <th...@redhat.com> --- tests/qtest/libqtest.c | 1 + 1 file changed, 1 insertion(+) diff --git a/tests/qtest/libqtest.c b/tests/qtest/libqtest.c index be0fb430dd..e49f3a1e45 100644 --- a/tests/qtest/libqtest.c +++ b/tests/qtest/libqtest.c @@ -545,6 +545,7 @@ redo: } } else { g_strfreev(words); + words = NULL; } return words; -- 2.18.4