Running unit tests under the Valgrind may help to detect QEMU memory issues (suggested by Denis V. Lunev). Some of the Valgrind reports relate to the unit test code itself. Let's eliminate the detected memory issues to ease locating critical ones.
Andrey Shinkevich (3): test-throttle: Fix uninitialized use of burst_length tests: Fix uninitialized byte in test_visitor_in_fuzz i386/kvm: initialize struct at full before ioctl call target/i386/kvm.c | 3 +++ tests/test-string-input-visitor.c | 8 +++----- tests/test-throttle.c | 2 ++ 3 files changed, 8 insertions(+), 5 deletions(-) -- 1.8.3.1
