[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #51413] core dump when started via Alt-F2

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #51413] core dump when started via Alt-F2
Date: Fri, 7 Jul 2017 17:03:18 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0

Follow-up Comment #2, bug #51413 (project octave):

Matthias responded via mail (please use the web interface, reply by mail does
> 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?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]