contrib/plugins/execlog: Explicitly check for qemu_plugin_read_register() failure
In insn_check_regs() we don't explicitly check whether
qemu_plugin_read_register() failed, which confuses Coverity into
thinking that sz can be -1 in the memcmp(). In fact the assertion
that sz == reg->last->len means this can't happen, but it's clearer
to both humans and Coverity if we explicitly assert that sz > 0, as
we already do in init_vcpu_register().
Coverity: CID 1611901, 1611902
Fixes: af6e4e0a22 ("contrib/plugins: extend execlog to track register changes")
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Message-ID: <20250710144543.1187715-1-peter.maydell@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-ID: <20250922093711.2768983-17-alex.bennee@linaro.org>
This commit is contained in:
parent
c9e79557e4
commit
04387b4a05
1 changed files with 1 additions and 0 deletions
|
|
@ -95,6 +95,7 @@ static void insn_check_regs(CPU *cpu)
|
|||
|
||||
g_byte_array_set_size(reg->new, 0);
|
||||
sz = qemu_plugin_read_register(reg->handle, reg->new);
|
||||
g_assert(sz > 0);
|
||||
g_assert(sz == reg->last->len);
|
||||
|
||||
if (memcmp(reg->last->data, reg->new->data, sz)) {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue