On 210118 1030, Thomas Huth wrote:
> On 18/01/2021 09.43, Paolo Bonzini wrote:
> > On 17/01/21 21:10, Alexander Bulekov wrote:
> > > This is useful for building reproducers. Instead checking the code or
> > > the QEMU_FUZZ_ARGS, the arguments are at the top of the crash log.
> > >
> > >
On 18/01/21 10:30, Thomas Huth wrote:
Hi Alexander, can you send _me_ a pull request for all the pending
fuzzing patches? I haven't paid much attention, but I have seen
external contributions and I have the feeling that they aren't being
applied/reviewed promptly.
I'm normally taking the
On 18/01/2021 09.43, Paolo Bonzini wrote:
On 17/01/21 21:10, Alexander Bulekov wrote:
This is useful for building reproducers. Instead checking the code or
the QEMU_FUZZ_ARGS, the arguments are at the top of the crash log.
Signed-off-by: Alexander Bulekov
---
tests/qtest/fuzz/fuzz.c | 11
On 17/01/21 21:10, Alexander Bulekov wrote:
This is useful for building reproducers. Instead checking the code or
the QEMU_FUZZ_ARGS, the arguments are at the top of the crash log.
Signed-off-by: Alexander Bulekov
---
tests/qtest/fuzz/fuzz.c | 11 ++-
1 file changed, 10
On 17/01/2021 21.10, Alexander Bulekov wrote:
This is useful for building reproducers. Instead checking the code or
the QEMU_FUZZ_ARGS, the arguments are at the top of the crash log.
Signed-off-by: Alexander Bulekov
---
tests/qtest/fuzz/fuzz.c | 11 ++-
1 file changed, 10
This is useful for building reproducers. Instead checking the code or
the QEMU_FUZZ_ARGS, the arguments are at the top of the crash log.
Signed-off-by: Alexander Bulekov
---
tests/qtest/fuzz/fuzz.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git
