[Octave-bug-tracker] [bug #58159] Octave GUI closes shortly after opening - signal 6

[Lee Strobel]

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

Ok, so I ran octave in gdb with debugging symbols. I set the
'follow-fork-mode' to 'child' to follow the child process after the fork. I'm
not exactly the world's most experienced debugger, but from what I can see,
octave-gui is spawning a bunch of threads, some of which are then crashing
fairly quickly for some reason. This is the output I got from my debug run,
including a stack trace after the crash:

Reading symbols from octave...
Reading symbols from /usr/lib/debug/usr/bin/octave-5.2.0.debug...
(gdb) set follow-fork-mode child
(gdb) run --gui
Starting program: /usr/bin/octave --gui
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Attaching after Thread 0xb6ff7be0 (LWP 30193) fork to child process 30196]
[New inferior 2 (process 30196)]
[Detaching after fork from parent process 30193]
[Inferior 1 (process 30193) detached]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
process 30196 is executing new program:
/usr/lib/octave/5.2.0/exec/armv7l-unknown-linux-gnueabihf/octave-gui
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0xaddba2f0 (LWP 30197)]
[New Thread 0xac3892f0 (LWP 30198)]
[New Thread 0xab9ff2f0 (LWP 30199)]
[New Thread 0xaafff2f0 (LWP 30200)]
[New Thread 0xaa5ff2f0 (LWP 30201)]
[New Thread 0xa9bff2f0 (LWP 30202)]
[New Thread 0xa90f32f0 (LWP 30203)]
[New Thread 0xa02ff2f0 (LWP 30204)]
[New Thread 0x9fafe2f0 (LWP 30205)]
[New Thread 0x9f2fd2f0 (LWP 30206)]
[New Thread 0x9eafc2f0 (LWP 30207)]
[New Thread 0x9e2fb2f0 (LWP 30208)]
[New Thread 0x9dafa2f0 (LWP 30209)]
[New Thread 0x9d2f92f0 (LWP 30210)]
[New Thread 0x9caf82f0 (LWP 30211)]
[New Thread 0x9b2f62f0 (LWP 30212)]
[New Thread 0x9aaf52f0 (LWP 30213)]
[New Thread 0x9a2f42f0 (LWP 30214)]
[New Thread 0x99af32f0 (LWP 30215)]
[Thread 0x99af32f0 (LWP 30215) exited]
[Thread 0x9a2f42f0 (LWP 30214) exited]
[New Thread 0x9a2f42f0 (LWP 30216)]
[Thread 0xa90f32f0 (LWP 30203) exited]

--Type <RET> for more, q to quit, c to continue without paging--
Thread 2.1 "octave-gui" received signal SIGABRT, Aborted.
[Switching to Thread 0xae683cb0 (LWP 30196)]
0xb47cc19c in raise () from /usr/lib/libc.so.6
(gdb) where
#0  0xb47cc19c in raise () at /usr/lib/libc.so.6
#1  0xb47b5864 in abort () at /usr/lib/libc.so.6
#2  0xb1c73284 in QMessageLogger::fatal(char const*, ...) const ()
    at /usr/lib/libQt5Core.so.5
#3  0xb1c72cc0 in qt_assert_x(char const*, char const*, char const*, int) ()
    at /usr/lib/libQt5Core.so.5
#4  0xb6de1828 in QList<QString>::at(int) const (i=0, this=0xbeffefa8)
    at libgui/src/main-window.cc:1467
#5  octave::main_window::handle_octave_ready() (this=this@entry=0x574508)
    at libgui/src/main-window.cc:1475
#6  0xb6e6ca80 in octave::main_window::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**)
    (_o=0x574508, _c=<optimized out>, _id=<optimized out>, _a=0x142ca4c)
    at libgui/src/moc-main-window.cc:729
#7  0xb1eb77c4 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#8  0xb2849204 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5
#9  0x0000000c in  ()


Let me know if that helps, or if there are any other commands I can run, which
would be helpful.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58159>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/