[pulseaudio-discuss] Results of valgrinding today's git version of pulseaudio

[Arun Raghavan]

On Sun, 22 May 2016, at 02:21 AM, Alexander E. Patrakov wrote:
> When starting pulseaudio under valgrind, I get this:
> 
> ==10853== Conditional jump or move depends on uninitialised value(s)
> ==10853==    at 0x5C91288: shm_attach (shm.c:380)
> ==10853==    by 0x5C91B68: pa_shm_cleanup (shm.c:453)
> ==10853==    by 0x5C91D4C: sharedmem_create (shm.c:150)
> ==10853==    by 0x5C91D4C: pa_shm_create_rw (shm.c:239)
> ==10853==    by 0x5C82193: pa_mempool_new (memblock.c:848)
> ==10853==    by 0xF23FFF7: setup_srbchannel (protocol-native.c:2634)
> ==10853==    by 0xF23FFF7: command_auth (protocol-native.c:2864)
> ==10853==    by 0x5C8989E: pa_pdispatch_run (pdispatch.c:346)
> ==10853==    by 0xF2426C4: pstream_packet_callback
> (protocol-native.c:4989)
> ==10853==    by 0x5C8C216: do_read (pstream.c:987)
> ==10853==    by 0x5C8EEF3: do_pstream_read_write (pstream.c:227)
> ==10853==    by 0x510040B: dispatch_pollfds (mainloop.c:655)
> ==10853==    by 0x510040B: pa_mainloop_dispatch (mainloop.c:898)
> ==10853==    by 0x510080B: pa_mainloop_iterate (mainloop.c:929)
> ==10853==    by 0x51008AF: pa_mainloop_run (mainloop.c:944)
> ==10853==
> ==10853== Conditional jump or move depends on uninitialised value(s)
> ==10853==    at 0x5C8C91D: pa_cmsg_ancil_data_close_fds (pstream.c:193)
> ==10853==    by 0x5C8DE57: do_write (pstream.c:759)
> ==10853==    by 0x5C8EEB7: do_pstream_read_write (pstream.c:233)
> ==10853==    by 0x510040B: dispatch_pollfds (mainloop.c:655)
> ==10853==    by 0x510040B: pa_mainloop_dispatch (mainloop.c:898)
> ==10853==    by 0x510080B: pa_mainloop_iterate (mainloop.c:929)
> ==10853==    by 0x51008AF: pa_mainloop_run (mainloop.c:944)
> ==10853==    by 0x406E3B: main (main.c:1141)
> ==10853==
> ==10853== Conditional jump or move depends on uninitialised value(s)
> ==10853==    at 0x5C8C91D: pa_cmsg_ancil_data_close_fds (pstream.c:193)
> ==10853==    by 0x5C8CA90: item_free (pstream.c:371)
> ==10853==    by 0x5C8DDC2: do_write (pstream.c:775)
> ==10853==    by 0x5C8EEB7: do_pstream_read_write (pstream.c:233)
> ==10853==    by 0x510040B: dispatch_pollfds (mainloop.c:655)
> ==10853==    by 0x510040B: pa_mainloop_dispatch (mainloop.c:898)
> ==10853==    by 0x510080B: pa_mainloop_iterate (mainloop.c:929)
> ==10853==    by 0x51008AF: pa_mainloop_run (mainloop.c:944)
> ==10853==    by 0x406E3B: main (main.c:1141)
> ==10853==
> 
> Can anyone familiar with this code look whether this is a bug or a false 
> positive?
> 
> Memory leaks (when I get a good summary of them) will be reported 
> separately.

I tried zero-initialising the relevant structures but that didn't help.
Not really sure what might be happening here.

-- Arun