[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: anonymous
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 05:02:46 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0

Follow-up Comment #5, bug #52996 (project octave):

At first I thought Octave would always crash, but it does not.
But I cannot find a consistent pattern.

Sometimes it crashes, sometimes it does not.
It seems to crash more often with the USB device than with the dummy device.
And it seems to crash more often when starting octave-cli manually, then type
"audiodevinfo" and then "exit" (instead of running "octave-cli --eval

I manually installed the octave and liboctave ddeb files.
I was not able to produce a stack trace: When I start GDB from within
> system (sprintf ("gnome-terminal --command 'gdb -p %d'", getpid ()),
I cannot type in the octave terminal anymore.
Last words of GDB here are:

Reading symbols from
symbols from
0x00007fc3eacb99cc in __pselect (nfds=1, readfds=0x7ffdfe176420, writefds=0x0,

    exceptfds=0x0, timeout=<optimized out>, sigmask=<optimized out>)
    at ../sysdeps/unix/sysv/linux/pselect.c:69
69      ../sysdeps/unix/sysv/linux/pselect.c: Datei oder Verzeichnis nicht

However, I achieved to run and crash the octave with valgrind (output
Maybe the output already helps.


(file #43205)

Additional Item Attachment:

File name: octave-crash-dbg-valgrind.txt  Size:37 KB


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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