[Octave-bug-tracker] [bug #59432] Octave exits with error code 3 for Bode plot

[John W. Eaton]

Follow-up Comment #53, bug #59432 (project octave):

Right, I guess we'll need to push the change and wait for a binary to be
available for testing by someone who was able to trigger the crash.

The thing the patch attempts to avoid is having the stack pointer altered
somehow between the time the unwind protect is set up and when it is executed
(though I don't know how or where that is happening).

So instead of relying on the stack pointer position, we just grab a reference
to the frame that is current when the function is executing and clear that
directly instead of looking at the current stack frame at the time the unwind
protect object is deleted.

I'll push a patch soon.  I'm also thinking about making the
stack_frame::clear_values method not cause a panic if it is called.

    _______________________________________________________

Reply to this item at:

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

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