[linux-audio-dev] What valgrind says

[Paul Davis]

On Sat, 2006-06-24 at 23:26 +0100, james at dis-dot-dat.net wrote:
> Hi peeps.
> 
> I've just been running an app through valgrind and I'm getting a few
> of these:
> 
> ==11955== Syscall param write(buf) points to uninitialised byte(s)
> ==11955==    at 0x4D51BDB: (within /lib64/libpthread-2.4.so)
> ==11955==    by 0x4B27CDD: (within /usr/lib64/libjack.so.0.0.23)
> ==11955==    by 0x4B29434: jack_deactivate (in
> /usr/lib64/libjack.so.0.0.23)
> ==11955==    by 0x4B2945F: jack_client_close (in
> /usr/lib64/libjack.so.0.0.23)
> ==11955==    by 0x40402F: jackpart_close() (jackPart.cc:86)
> ==11955==    by 0x40235F: mainLoop() (sampleplayer.cpp:438)
> ==11955==    by 0x40237B: main (sampleplayer.cpp:444)
> ==11955==  Address 0x7FEFFE934 is on thread 1's stack
> 
> 
> I can't see anything wrong on my part, so I thought I'd check with
> people who know more than I before I tear my program apart.
> 
> I also get them coming from jack_port_register, jack_activate and
> jack_connect.

they don't matter. they are the result of writing a byte to a FIFO to
wake up an(other) client. the contents of the byte do not make any
difference at any point.

--p