[Top][All Lists]

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

[Octave-bug-tracker] [bug #53156] examples/code/make_int.cc produces a s

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #53156] examples/code/make_int.cc produces a segfault at exit of Octave
Date: Tue, 20 Feb 2018 15:00:49 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Update of bug #53156 (project octave):

                  Status:               Confirmed => Ready For Test         


Follow-up Comment #11:

I checked in the following changeset.


Although it avoids the crash for me, but it is definitely not a proper fix. 
The core issue is that we still don't have resource management right in the

The situation is made more complex by things like dynamically loaded data
types and classdef objects that might run destructors.  I'm not sure what the
best solution is.  I'd like to be able to have all resource initialization for
the interpreter handled by the interpreter constructor and all resource
cleanup be handled by the corresponding destructor.  Likewise for all the
objects that make up the interpreter.  It seems like that should be possible,
but we are definitely not there yet.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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