[pulseaudio-discuss] Trying to debug segfault in pa_mainloop_dispatch().
rtepub at gmail.com
Fri Jul 28 17:30:26 UTC 2017
I also wanted to ask about the logging - is it enough to export the symbols
I'm finding at
before running my application, or do I also need to restart the pulseaudio
deamon with something like '--log-target=syslog'? Right now I'm doing both
and seeing some output, though I don't know which part is required, or both.
On Fri, Jul 28, 2017 at 9:50 AM, Rich Eakin <rtepub at gmail.com> wrote:
> 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
> #1 0x00007ffff61454bc in pa_mainloop_iterate () from
> #2 0x00007ffff6145560 in pa_mainloop_run () from
> #3 0x00007ffff61537a9 in ?? () from /usr/lib/x86_64-linux-gnu/
> #4 0x00007ffff0ef0078 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/
> #5 0x00007ffff58416ba in start_thread () from /lib/x86_64-linux-gnu/
> #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:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pulseaudio-discuss