[Octave-bug-tracker] [bug #52996] calling audiodevinfo() results in a segfault on exit when JACK sound server is running

[anonymous]

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
'audiodevinfo'"

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

Reading symbols from
/usr/lib/x86_64-linux-gnu/octave/4.2.1/oct/x86_64-pc-linux-gnu/__init_gnuplot__.oct...Reading
symbols from
/usr/lib/debug/.build-id/fc/0ba7125263e7e95eab390a739e3604f6faf553.debug...done.
done.
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
gefunden.
(gdb) 


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

Best,
Marc




(file #43205)
    _______________________________________________________

Additional Item Attachment:

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


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52996>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/