bugGNU Octave - Bugs: bug #58159, Octave GUI closes shortly after...

 
 

bug #58159: Octave GUI closes shortly after opening - signal 6

Submitter:  None
Submitted:  Sat 11 Apr 2020 10:50:26 AM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Unexpected Error or Warning
Status:  None Assigned to:  None
Originator Name:  Time4Tea Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 5.2.0
Operating System:  * GNU/Linux Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 09 Mar 2021 11:29:53 PM UTC, comment #9: 

This report is against an old version of Octave that is no longer supported.  Please try the latest stable version (6.2.) as there have been a lot of improvements.

Rik <rik5>
Group administrator
Wed 15 Apr 2020 02:11:25 AM UTC, comment #8: 

I have another GUI application installed that uses Qt and seems to be stable. I'll see if I can do a bit more debugging over the next few days, although debugging this sort of complex, multi-threaded program is stretching my experience/abilities a bit.

Lee Strobel <time4tea>
Mon 13 Apr 2020 02:51:06 PM UTC, comment #7: 

It might be a problem of Qt on ARM. You could google the gdb messages.

Alternatively, download the debug versions of the libraries.

Mark van Rossum <cosine>
Mon 13 Apr 2020 12:16:38 AM UTC, comment #6: 

The following threads seem to still be running after the program stopped:

(gdb) info inferiors
  Num  Description       Executable       
  1    <null>            /usr/lib/octave/5.2.0/exec/armv7l-unknown-linux-gnueabihf/octave-gui

  • 2    process 30196     /usr/lib/octave/5.2.0/exec/armv7l-unknown-linux-gnueabihf/octave-gui

(gdb) info threads
  Id   Target Id                                       Frame

  • 2.1  Thread 0xae683cb0 (LWP 30196) "octave-gui"      0xb47cc19c in raise ()

   from /usr/lib/libc.so.6
  2.2  Thread 0xaddba2f0 (LWP 30197) "QXcbEventQueue"  0xb486d67c in poll ()
   from /usr/lib/libc.so.6
  2.3  Thread 0xac3892f0 (LWP 30198) "gmain"           0xb486d67c in poll ()
   from /usr/lib/libc.so.6
  2.4  Thread 0xab9ff2f0 (LWP 30199) "gdbus"           0xb486d67c in poll ()
   from /usr/lib/libc.so.6
  2.5  Thread 0xaafff2f0 (LWP 30200) "QDBusConnection" 0xb486d67c in poll ()
   from /usr/lib/libc.so.6
  2.6  Thread 0xaa5ff2f0 (LWP 30201) "SelfListener"    0xb4873f4c in syscall ()
   from /usr/lib/libc.so.6
  2.7  Thread 0xa9bff2f0 (LWP 30202) "QFileInfoGather" 0xb17d7e50 in pthread_cond_wait@@GLIBC_2.4 () from /usr/lib/libpthread.so.0
  2.9  Thread 0xa02ff2f0 (LWP 30204) "llvmpipe-0"      0xb17d7e50 in pthread_cond_wait@@GLIBC_2.4 () from /usr/lib/libpthread.so.0
  2.10 Thread 0x9fafe2f0 (LWP 30205) "llvmpipe-1"      0xb17d7e50 in pthread_cond_wait@@GLIBC_2.4 () from /usr/lib/libpthread.so.0
  2.11 Thread 0x9f2fd2f0 (LWP 30206) "llvmpipe-2"      0xb17d7e50 in pthread_cond_wait@@GLIBC_2.4 () from /usr/lib/libpthread.so.0
  2.12 Thread 0x9eafc2f0 (LWP 30207) "llvmpipe-3"      0xb17d7e50 in pthread_cond_wait@@GLIBC_2.4 () from /usr/lib/libpthread.so.0
  2.13 Thread 0x9e2fb2f0 (LWP 30208) "octave-gui"      0xb17d7e50 in pthread_cond_wait@@GLIBC_2.4 () from /usr/lib/libpthread.so.0
  2.14 Thread 0x9dafa2f0 (LWP 30209) "octave-gui"      0xb17d7e50 in pthread_cond_wait@@GLIBC_2.4 () from /usr/lib/libpthread.so.0
  2.15 Thread 0x9d2f92f0 (LWP 30210) "octave-gui"      0xb17d7e50 in pthread_cond_wait@@GLIBC_2.4 () from /usr/lib/libpthread.so.0
  2.16 Thread 0x9caf82f0 (LWP 30211) "octave-gui"      0xb17d7e50 in pthread_cond_wait@@GLIBC_2.4 () from /usr/lib/libpthread.so.0
  2.17 Thread 0x9b2f62f0 (LWP 30212) "QThread"         0xb4870ab0 in select ()
   from /usr/lib/libc.so.6
  2.18 Thread 0x9aaf52f0 (LWP 30213) "QThread"         0xb47cd044 in sigtimedwait
    () from /usr/lib/libc.so.6
--Type <RET> for more, q to quit, c to continue without paging--
  2.21 Thread 0x9a2f42f0 (LWP 30216) "fulltextsearch:" 0xb4863f34 in pwrite64 ()
   from /usr/lib/libc.so.6

Lee Strobel <time4tea>
Mon 13 Apr 2020 12:12:00 AM UTC, comment #5: 

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.

Lee Strobel <time4tea>
Sun 12 Apr 2020 04:27:43 PM UTC, comment #4: 
Mark van Rossum <cosine>
Sun 12 Apr 2020 03:47:02 PM UTC, comment #3: 

Ok, thank you both for your advice. I will try running it with debugging symbols and get back to you.

comment #2:

>
> If you have trouble, you might find it more effective to attach gdb to the octave-gui process that the octave executable execs.
>


Ok. How would I go about doing that?

Lee Strobel <time4tea>
Sat 11 Apr 2020 04:18:01 PM UTC, comment #2: 

Because of the way Octave must start a separate process for the GUI to make programs like "less" work in the GUI terminal widget, "gdb octave" may not work as you expect.

If you have trouble, you might find it more effective to attach gdb to the octave-gui process that the octave executable execs.


John W. Eaton <jwe>
Group administrator
Sat 11 Apr 2020 02:05:14 PM UTC, comment #1: 

Build with debug symbols and then run with
gdb octave
run

Mark van Rossum <cosine>
Sat 11 Apr 2020 10:50:26 AM UTC, original submission:  

Hi, I am having a problem with Octave that I am running on Parabola GNU/Linux on an armv7 Chromebook (OpenRC). Octave seems to run fine in CLI mode; however, if I try to run the GUI, it opens and then closes again after a few seconds, with the error:

octave exited with signal 6

I experience the problem in both Mate and LXDE. Other GUI applications are working fine. I have downloaded and built from the latest 5.2.0 source, but the problem still persists. Does anyone have any suggestions what might be causing the problem, or how I can view more debugging information?

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by time4tea (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by cosine (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-03-09 rik5 Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code