[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #60365] segfault at exit after "test audiodevi
|
From: |
Rik |
|
Subject: |
[Octave-bug-tracker] [bug #60365] segfault at exit after "test audiodevinfo" |
|
Date: |
Sat, 10 Apr 2021 19:50:55 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36 |
Follow-up Comment #1, bug #60365 (project octave):
How do we know that this is an Octave issue versus a PipeWire issue? If
PipeWire is new it seems more likely that they didn't implement the interface
with PortAudio correctly.
According to gdb, it is thread 19 which caused the SIGSEGV. Looking at that
thread, I see
Thread 19 (Thread 0x7fff529c4640 (LWP 318506) "QThread"):
#0 0x00007fff4f66acb0 in ()
#1 0x00007fff4f58e0fb in loop_iterate () at
/usr/lib64/spa-0.2/support/libspa-support.so
#2 0x00007fff4f5cbd13 in do_loop () at /lib64/libpipewire-0.3.so.0
#3 0x00007fffee7d6299 in start_thread () at /lib64/libpthread.so.0
#4 0x00007fffee6fe6a3 in clone () at /lib64/libc.so.6
It is definitely the pipewire library. I suppose it is possible that Octave
is not calling a PortAudio command to shut things down before exiting, but I
don't know very much about PortAudio.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60365>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/