[Octave-bug-tracker] [bug #59228] embedded.cc example crashes with segfault

[John W. Eaton]

Follow-up Comment #24, bug #59228 (project octave):

Thinking about this more, even if allocated memory remains valid until after
all the destructors are called, Octave also has a number of global objects
that could cause trouble.  Is there any guarantee about the order that they
are deleted?  Is it possible that some of those global objects are deleted
before the singleton destructor calls the interpreter shutdown method and
destructor?  When the interpreter shutdown method is called, it needs to be
able to execute arbitrary functions.  We can't expect that to work if some
necessary global objects have already been destroyed.

If this is correct, then it seems to me that we can't expect the interpreter
destructor to properly shut down after main returns until we can ensure that
the shutdown process doesn't rely on any global or static(?) variables.

    _______________________________________________________

Reply to this item at:

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

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