bugGNU Octave - Bugs: bug #51413, core dump when started via Alt-F2

 
 

bug #51413: core dump when started via Alt-F2

Submitted by:  None
Submitted on:  Fri 07 Jul 2017 12:43:43 PM UTC  
 
Category:  Performance Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  Works For Me Assigned to:  None
Originator Name:  Matthias Bodenbinder Originator Email:  -email is unavailable-
Open/Closed:  Closed Release:  4.2.1
Operating System:  GNU/Linux

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Mon 17 Jul 2017 05:45:54 PM UTC, comment #4: 

Closing as works for me, there doesn't seem to be a reproducible case for a segfault when Octave is launched from the desktop shell.

Mike Miller <mtmiller>
Project Administrator
Fri 07 Jul 2017 09:08:22 PM UTC, comment #3: 

I brute forced in a shell

$ while true; do pid=$(pgrep octave-gui); if [ -n "$pid" ]; then gdb -p $pid; fi; done

and was able to attach with gdb. Octave exits cleanly for me when it is run from the Gnome Alt-F2 "Enter a Command" prompt. So definitely unable to reproduce here.

Mike Miller <mtmiller>
Project Administrator
Fri 07 Jul 2017 09:03:18 PM UTC, comment #2: 

Matthias responded via mail (please use the web interface, reply by mail does nothing):

> That is working!
>
> Alt-F2 -> octave --force-gui
>
> Thank you!
>
> But from a user experience point of view this is bad behaviour. octave should detect that a GUI is needed.


True. Which is why we ship a .desktop file by default that specifies "Exec=octave --force-gui".

Octave runs in a variety of different ways, as a script interpreter, as an interactive program, and it needs to support all of those in a balanced way. If you can suggest how to make Octave start the GUI without needing to specify the --force-gui option when not running from a terminal while still supporting other modes of operation, please do contribute a patch.

I think this is worth keeping open, because Octave should not crash, even when it decides that it has nothing to do based on the execution environment.

I can't reproduce the crash in the Gnome desktop, or I don't know if I can, because I can't see a crash or it's being suppressed. When I run "octave" from outside a terminal, Octave runs and exits and I have no way to know whether it exited cleanly or crashed. Does anyone have ideas about how to capture the output or attach gdb to Octave when it's running asynchronously and exiting quickly outside of a terminal?

Please help by providing some more details, maybe by installing debug symbols from your distribution and providing a more detailed stack dump?

Mike Miller <mtmiller>
Project Administrator
Fri 07 Jul 2017 06:15:51 PM UTC, comment #1: 

What are you entering in the command box to run octave? Have you tried "octave --force-gui"?

Mike Miller <mtmiller>
Project Administrator
Fri 07 Jul 2017 12:43:43 PM UTC, original submission:  

I can run octave out of a terminal. That works fine. But when I use the Alt-F2 dialog of the cinnamon desktop octave is generating a core dump. The same is true with MATE desktop.

I am using Manjaro.

Jul 07 14:41:10 manjaro systemd-coredump[28187]: Process 28182 (octave-gui) of user 1000 dumped core.

                                                

                                                 Stack trace of thread 28182:
                                                 #0  0x00007fb0abb0f670 raise (libc.so.6)
                                                 #1  0x00007fb0abb10d00 abort (libc.so.6)
                                                 #2  0x00007fb0ae38475e n/a (liboctinterp.so.4)
                                                 #3  0x00007fb0abb0f6f0 __restore_rt (libc.so.6)
                                                 #4  0x00007fb0ae2557cf n/a (liboctinterp.so.4)
                                                 #5  0x00007fb0ae258778 _Z16dump_octave_corev (liboctinterp.so.4)
                                                 #6  0x00007fb0ae3846a3 n/a (liboctinterp.so.4)
                                                 #7  0x00007fb0abb0f6f0 __restore_rt (libc.so.6)
                                                 #8  0x00007fb0abb0f670 raise (libc.so.6)
                                                 #9  0x00007fb0abb10d00 abort (libc.so.6)
                                                 #10 0x00007fb0a9c78807 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
                                                 #11 0x00007fb0a9c8777d _ZN7QThreadD2Ev (libQt5Core.so.5)
                                                 #12 0x00007fb0a9c87859 _ZN7QThreadD0Ev (libQt5Core.so.5)
                                                 #13 0x00007fb0aea17611 _ZN14octave_qt_linkD1Ev (liboctgui.so.2)
                                                 #14 0x00007fb0aea176b9 _ZN14octave_qt_linkD0Ev (liboctgui.so.2)
                                                 #15 0x00007fb0aea0d410 _ZN11main_windowD1Ev (liboctgui.so.2)
                                                 #16 0x00007fb0aea16a76 _ZN6octave15gui_application7executeEv (liboctgui.so.2)
                                                 #17 0x00000000004010d8 n/a (octave-gui)
                                                 #18 0x00007fb0abafc43a __libc_start_main (libc.so.6)
                                                 #19 0x000000000040142a n/a (octave-gui)

                                                

                                                 Stack trace of thread 28185:
                                                 #0  0x00007fb0abbbf24d poll (libc.so.6)
                                                 #1  0x00007fb0a17bbbf9 n/a (libglib-2.0.so.0)
                                                 #2  0x00007fb0a17bbd0c g_main_context_iteration (libglib-2.0.so.0)
                                                 #3  0x00007fb0a9ebfe7f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
                                                 #4  0x00007fb0a9e6621a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
                                                 #5  0x00007fb0a9c8840a _ZN7QThread4execEv (libQt5Core.so.5)
                                                 #6  0x00007fb097c19d45 n/a (libQt5DBus.so.5)
                                                 #7  0x00007fb0a9c8ccbd n/a (libQt5Core.so.5)
                                                 #8  0x00007fb0a885b297 start_thread (libpthread.so.0)
                                                 #9  0x00007fb0abbc91ef __clone (libc.so.6)

                                                

                                                 Stack trace of thread 28183:
                                                 #0  0x00007fb0abbbf24d poll (libc.so.6)
                                                 #1  0x00007fb09fb598e0 n/a (libxcb.so.1)
                                                 #2  0x00007fb09fb5b679 xcb_wait_for_event (libxcb.so.1)
                                                 #3  0x00007fb0980cbd49 n/a (libQt5XcbQpa.so.5)
                                                 #4  0x00007fb0a9c8ccbd n/a (libQt5Core.so.5)
                                                 #5  0x00007fb0a885b297 start_thread (libpthread.so.0)
                                                 #6  0x00007fb0abbc91ef __clone (libc.so.6)

                                                

                                                 Stack trace of thread 28184:
                                                 #0  0x00007fb0abbbf24d poll (libc.so.6)
                                                 #1  0x00007fb0a17bbbf9 n/a (libglib-2.0.so.0)
                                                 #2  0x00007fb0a17bbd0c g_main_context_iteration (libglib-2.0.so.0)
                                                 #3  0x00007fb0a9ebfe7f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
                                                 #4  0x00007fb0a9e6621a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
                                                 #5  0x00007fb0a9c8840a _ZN7QThread4execEv (libQt5Core.so.5)
                                                 #6  0x00007fb0a9c8ccbd n/a (libQt5Core.so.5)
                                                 #7  0x00007fb0a885b297 start_thread (libpthread.so.0)
                                                 #8  0x00007fb0abbc91ef __clone (libc.so.6)

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 None (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

     

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-02-26 mtmiller Carbon-CopyRemoved 80942 => -
    2017-07-17 mtmiller StatusNeed Info => Works For Me
        Open/ClosedOpen => Closed
    2017-07-07 mtmiller StatusNone => Need Info

    Back to the top


    Powered by Savane 3.5