[Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode

[Mike Miller]

Follow-up Comment #4, bug #50068 (project octave):

It seems that when octave_main returns, the interpreter object has been
destroyed. It has gone through its command line processing and initialization
of its internal state, but then it exits and cleans itself up. The subsequent
call to eval_string is trying to operate on an interpreter that doesn't exist
anymore. This was not the case in Octave 4.0.x, because the interpreter was
not an object with contained state, it was just initializing a bunch of
globals.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?50068>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/