https://bugs.kde.org/show_bug.cgi?id=417993
--- Comment #12 from Mark Wielaard <m...@klomp.org> ---
I think your analysis is correct. We already seem to do this when printing out
a complaint about a real mismatch.
See memcheck/tests/vbits-test/util.c (print_opnd):
/* The value itself might be partially or fully undefined, so take a
copy, paint the copy as defined, and print the copied value. This is
so as to avoid error messages from Memcheck, which are correct, but
confusing. */
And testing your 3 line fix on s390x it does seem to work as expected:
$ perl tests/vg_regtest memcheck/tests/vbit-test/vbit-test.vgtest
vbit-test: valgrind -q --expensive-definedness-checks=yes ./vbit-test
== 1 test, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB
failures, 0 post failures ==
I think my only question is whether we should "clear" all of data or just the
value fields of the result and opnds[] of the test_data_t?
I guess it doesn't matter whether the rest of the test_data_t struct values are
cleared too, but it might "hide" other/real bugs?
--
You are receiving this mail because:
You are watching all bug changes.
