octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #59628] Segmentation fault on GUI close


From: Lars Kindermann
Subject: [Octave-bug-tracker] [bug #59628] Segmentation fault on GUI close
Date: Fri, 18 Dec 2020 08:41:09 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Follow-up Comment #25, bug #59628 (project octave):

Actually, I use the combination --gui --eval without --persist intentionally.

I start scripts automatically in the background that will generate graphics
and text output (shown in the command window) and finally wait() till I close
the figure or the gui. In case of an error, octave exits and the calling shell
script handles the case.

Now I dont see the command window any more because --gui is ignored and if, as
suggested, --gui would imply --persist, an error won't antomatically exit and
the gui hang around forever.

Of course the desired behaviour could be achieved by modifying the workflow,
but the current logic of --gui and --persist has reasonable use cases. So I
opt for keeping the old behaviour.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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