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: Torsten Lilge
Subject: [Octave-bug-tracker] [bug #59628] Segmentation fault on GUI close
Date: Sat, 12 Dec 2020 13:29:57 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36

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

It looks like pending signals cause this segfault if the slot's object is
already gone ("exit") when the signal is finally processed.

This brings me to the question if there are really case where it is required
to start the GUI without --persist option when a script or commands have to be
evaluated. If not, we could just ignore the --gui option in these cases or
force --persist if --gui is requested.
 

    _______________________________________________________

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]