As Alexander already wrote, this triggered the same bug as #1919036
which got fixed by commit 0ebb5fd80589835153a0c2baa1b8cc7a04e67a93.
Since this is not reproducible anymore, I'm closing this bug now. If you
still can reproduce it somehow, please open a new ticket in the new
gitlab issue tracker.
Can you still reproduce the issue with QEMU v6.0? For me, the attached
reproducer does not cause a crash anymore...
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
It looks like this reproducer triggers the same bug as #1919036, as of
3f8d1885e
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1907909
Title:
assertion failure in am53c974
Status in QEMU:
New
** Tags added: fuzzer
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1907909
Title:
assertion failure in am53c974
Status in QEMU:
New
Bug description:
Hello,
Using hypervisor fuzzer,
