<div dir="ltr">I also wanted to ask about the logging - is it enough to export the symbols I'm finding at <a href="https://freedesktop.org/software/pulseaudio/doxygen/index.html#logging_sec">https://freedesktop.org/software/pulseaudio/doxygen/index.html#logging_sec</a> before running my application, or do I also need to restart the pulseaudio deamon with something like '<span style="color:rgb(0,0,0);white-space:pre-wrap">--log-target=syslog'? Right now I'm doing both and seeing some output, though I don't know which part is required, or both.</span><div><span style="color:rgb(0,0,0);white-space:pre-wrap"><br></span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap">Thanks again,</span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap">RIch</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 28, 2017 at 9:50 AM, Rich Eakin <span dir="ltr"><<a href="mailto:rtepub@gmail.com" target="_blank">rtepub@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>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:</div><div><br></div><div>```</div><div>#0 0x00007ffff61451c9 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/<wbr>libpulse.so.0</div><div>#1 0x00007ffff61454bc in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/<wbr>libpulse.so.0</div><div>#2 0x00007ffff6145560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/<wbr>libpulse.so.0</div><div>#3 0x00007ffff61537a9 in ?? () from /usr/lib/x86_64-linux-gnu/<wbr>libpulse.so.0</div><div>#4 0x00007ffff0ef0078 in ?? () from /usr/lib/x86_64-linux-gnu/<wbr>pulseaudio/<a href="http://libpulsecommon-8.0.so" target="_blank">libpulsecommon-8.0.<wbr>so</a></div><div>#5 0x00007ffff58416ba in start_thread () from /lib/x86_64-linux-gnu/<wbr>libpthread.so.0</div><div>#6 0x00007ffff4cd63dd in clone () from /lib/x86_64-linux-gnu/libc.so.<wbr>6</div><div>```</div><div><br></div><div>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?</div><div><br></div><div>For reference, our usage of the pulseaudio backend is primarily here:</div><div><a href="https://github.com/cinder/Cinder/blob/master/include/cinder/audio/linux/ContextPulseAudio.h" target="_blank">https://github.com/cinder/<wbr>Cinder/blob/master/include/<wbr>cinder/audio/linux/<wbr>ContextPulseAudio.h</a><br></div><div><a href="https://github.com/cinder/Cinder/blob/master/src/cinder/audio/linux/ContextPulseAudio.cpp" target="_blank">https://github.com/cinder/<wbr>Cinder/blob/master/src/cinder/<wbr>audio/linux/ContextPulseAudio.<wbr>cpp</a><br></div><div><br></div><div>Thanks,</div><div>Rich</div></div>
</blockquote></div><br></div>