On 3/3/25 17:32, Peter Foley wrote:
The full output looks like:
Uninitialized bytes in strlen at offset 0 inside [0xd1958110, 5)
==9780==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0xc1c4b170 in tdb_hash third_party/qemu/qobject/qdict.c:46:31
#1 0xc1c4b4a4 in qd
On Sat, Mar 1, 2025 at 2:14 AM Markus Armbruster wrote:
> Paolo Bonzini writes:
>
> > On 2/28/25 22:20, Patrick Venture wrote:
> >> From: Peter Foley
> >> e.g.
> >> qemu: Uninitialized value was created by an allocation of
> 'key_in_cur.i' in the stack frame
> >> qemu: #0 0xc49f489c in keyv
Paolo Bonzini writes:
> On 2/28/25 22:20, Patrick Venture wrote:
>> From: Peter Foley
>> e.g.
>> qemu: Uninitialized value was created by an allocation of 'key_in_cur.i' in
>> the stack frame
>> qemu: #0 0xc49f489c in keyval_parse_one
>> third_party/qemu/util/keyval.c:190:5
>> Signed-off-b
On 2/28/25 22:20, Patrick Venture wrote:
From: Peter Foley
e.g.
qemu: Uninitialized value was created by an allocation of 'key_in_cur.i' in the
stack frame
qemu: #0 0xc49f489c in keyval_parse_one third_party/qemu/util/keyval.c:190:5
Signed-off-by: Peter Foley
Signed-off-by: Patrick Ventu
From: Peter Foley
e.g.
qemu: Uninitialized value was created by an allocation of 'key_in_cur.i' in the
stack frame
qemu: #0 0xc49f489c in keyval_parse_one third_party/qemu/util/keyval.c:190:5
Signed-off-by: Peter Foley
Signed-off-by: Patrick Venture
---
util/keyval.c | 2 +-
1 file chang
