[pulseaudio-discuss] Trying to debug segfault in pa_mainloop_dispatch().

[Rich Eakin]

Hi,

We have adopted use of the pulseaudio library in the framework I work on
(libcinder) and we are just beginning to do production work with it. I've
hit a snag however, and I'm searching for ways to debug. Very occasionally
(less than twice a day), I'm seeing the application segfault with the
following backtrace on the audio thread:

```
#0  0x00007ffff61451c9 in pa_mainloop_dispatch () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#1  0x00007ffff61454bc in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x00007ffff6145560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x00007ffff61537a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x00007ffff0ef0078 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/
libpulsecommon-8.0.so
#5  0x00007ffff58416ba in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#6  0x00007ffff4cd63dd in clone () from /lib/x86_64-linux-gnu/libc.so.6
```

I haven't been able to track down if we're doing something wrong from the
client side yet, though I was wondering if there is a way to turn on some
sort of verbosity to track this sort of thing, or it sticks out to some
folks as far as some things I can check?

For reference, our usage of the pulseaudio backend is primarily here:
https://github.com/cinder/Cinder/blob/master/include/cinder/audio/linux/ContextPulseAudio.h
https://github.com/cinder/Cinder/blob/master/src/cinder/audio/linux/ContextPulseAudio.cpp

Thanks,
Rich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20170728/ed7d7008/attachment.html>