On 6/26/06, Jack O'Quin <[EMAIL PROTECTED]> wrote:
OK, I see it now. All those uninitialized write complaints are due to
the fact that jack_request_t is a union. Most requests don't need (or
want) to fill in all the bytes, just the ones that matter for that
RequestType.
There are jack_request_t structs used all over the place. The only
solution I can think of that would make valgrind happy would be to
initialize them all to zeroes before filling them in. While that would
eliminate these complaints, I have some doubts that we really want
to make all those changes. There is some risk of introducing real
bugs while fixing them.
Those valgrind warnings really *are* annoying, of course.
--
joq
Use valgrind's --gen-suppressions=yes option, create a suppressions
file, and post it to the list for all to enjoy.
