[Octave-bug-tracker] [bug #49515] Octave aborts on exit under some conditions with --eval CODE

[Mike Miller]

URL:
  <http://savannah.gnu.org/bugs/?49515>

                 Summary: Octave aborts on exit under some conditions with
--eval CODE
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Wed 02 Nov 2016 09:08:25 AM PDT
                Category: Interpreter
                Severity: 4 - Important
                Priority: 5 - Normal
              Item Group: Crash
                  Status: Need Info
             Assigned to: mtmiller
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

I have a reproducible case for this error on exit, but unfortunately it is the
entire symbolic package test suite.


$ ./run-octave -g --eval "addpath ~/src/octave/octsympy/inst; exit
(octsympy_tests);"
(gdb) r
...
[Thread 0x7fffc9657700 (LWP 25243) exited]
pure virtual method called
terminate called without an active exception

Thread 10 "QThread" received signal SIGABRT, Aborted.


The abort occurs when `octave_link::exit (status)` is called by the
interpreter in the `clean_up_and_exit` method. The problem is that the
octave_link has been partially destroyed, it is no longer an octave_qt_link,
but the `instance` pointer still points to the same address. The `exit` method
is not implemented in the base class.

I have not yet figured out how the interpreter is still in `clean_up_and_exit`
while the GUI main function has already exited and the octave_qt_link has
already been destroyed.

The symbolic unit test suite exercises a lot of functionality, including
plotting figures, opening and closing files, keeping a persistent popen2
running in the background, so I haven't reduced this to a smaller reproducible
example yet. Just running one or two of the address@hidden method unit tests is 
not
enough to trigger this.




    _______________________________________________________

Reply to this item at:

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

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