Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset
fsateler at debian.org
Thu Mar 2 23:36:29 UTC 2017
Control: tags -1 = help
On Thu, Mar 2, 2017 at 8:01 PM, Linus Lüssing <linus.luessing at c0d3.blue> wrote:
> On Thu, Mar 02, 2017 at 06:29:12PM -0300, Felipe Sateler wrote:
>> Could you install the debug symbols for libsbc and see if we can get a
>> reasonable function name for that call?
> Thread 1 (Thread 0xa0c79300 (LWP 3283)):
> #0 0xa0c84962 in sbc_analyze_eight_armv6 () at sbc/sbc_primitives_armv6.c:115
> #1 0x000c0018 in ?? ()
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> (gdb) quit
> Hm, not sure it's relevant, but the "v6" in sbc_analyze_eight_armv6 /
> sbc_primitives_armv6.c looks weird. The Odroid U3 sports a Samsung
> Exynos 4412 which is ARMv7, not v6. (but not sure, maybe armv6 code
> was supposed to run under ARMv7, but not the other way round?)
> Otherwise sbc_primitives_armv6.c:115 looks like fun with Assembly
Indeed. However, from what I can see the most likely (only?) way to
get there is via a sbc_encode that is called in module-bluez5-device.
However, that part of the code does not look changed since 9.0. Have
you confirmed downgrading to 9.0 fixes the issue?
I'm CCing the bluetooth maintainers in case they have some idea of how
to debug this. I have no idea what could have caused this, and sbc has
very little documentation.
More information about the pkg-pulseaudio-devel