[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #52996] calling audiodevinfo() results in a se

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #52996] calling audiodevinfo() results in a segfault on exit when JACK sound server is running
Date: Thu, 8 Feb 2018 19:55:46 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0

Update of bug #52996 (project octave):

                  Status:            Works For Me => Confirmed              


Follow-up Comment #6:

I can reproduce this crash now with the following

$ jackd -d dummy -p 512 &
$ octave-cli
>> audiodevinfo;
>> clear functions;

The crash occurs on "clear functions", when the audiodevinfo oct file is
unloaded, and recursively the portaudio and jack libraries are unloaded.

This crash only occurs for me when the jack server is started with "-p 512" or
a lower number. With the default "-p 1024" or a higher value the crash does
not occur.

Can you verify those findings?

Btw if you are using octave-cli, you can use gdb with just "gdb --args
octave-cli" with whatever options and arguments following that.

But I'm not able to get a very useful backtrace from gdb. I think this is
because the error is related to the jack library creating threads in the
background and then octave unloading the portaudio library while these threads
are still active.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]