On Wed, Sep 06, 2017 at 16:10:25 +0200, Peter P. wrote: > The backtrace I provided was already with /usr/bin/octave --no-gui. I hope a > 'stack trace' is the same thing as a 'backtrace', at least gdb's help > text tells me so.
But 'octave --no-gui' is not the same thing as 'octave-cli'. I would like to see the backtrace with this crash occurring in 'octave-cli'. This backtrace: > (gdb) bt > #0 0x00007fffd8328bf0 in jack_thread_touch_stack () at thread.c:112 > #1 0x00007fffd8328fb9 in jack_thread_proxy (varg=0x7fffd44cfa80) at > thread.c:128 > #2 0x00007ffff44ee494 in start_thread () at > /lib/x86_64-linux-gnu/libpthread.so.0 > #3 0x00007ffff4232abf in clone () at /lib/x86_64-linux-gnu/libc.so.6 is not very helpful because it only shows a jack thread running, there is nothing there about what Octave is doing. Please try with 'octave-cli', with octave dbgsym packages installed as well, and use 'thread apply all bt' in gdb to be sure to capture all running threads. -- mike
signature.asc
Description: PGP signature
