[Octave-bug-tracker] [bug #58814] Abort, core dump on exiting from graphics code

[anonymous]

Follow-up Comment #13, bug #58814 (project octave):

All this is with Qt 5.15, Linux kernel 5.4.52, libc 2.31, using GCC 10.1.0 and
also when repeated with Clang 10.0.0.

Using "/usr/bin/time --verbose" is a hack to get info about programs that
crash on exit. This was the result for all three cases: the unpatched version,
applying patch 1 alone, and applying patch 1 + patch 2 both.


$ /usr/bin/time --verbose octave mytest.m 
warning: base_graphics_object::get_properties: invalid graphics object
terminate called after throwing an instance of 'std::bad_cast'
  what():  std::bad_cast
fatal: caught signal Aborted -- stopping myself...
Command terminated by signal 6
        Command being timed: "octave mytest.m"
        {{{ SNIP }}}
        Exit status: 0


It was terminated by signal 6 (SIGABRT) in all three cases, not a SIGSEGV.

Appending a "close all" (*note*: close all, not clear all) statement to the
very end of mytest.m doesn't let Octave exit until the figures are all closed,
and there's no SIGABRT:


$ time --verbose octave mytest.m 
        Command being timed: "octave mytest.m"
  {{{ SNIP }}}
        Exit status: 0


The foocls test, both with and without the sombrero, works perfectly with
patch1 alone, and also with patch1 + patch2. With the original unpatched
version it gives SIGABRT:


$ /usr/bin/time --verbose octave
 {{{ SNIP }}}

octave:1> foocls
ans =

  foocls object with properties:

octave:2> exit
pure virtual method called
terminate called without an active exception
fatal: caught signal Aborted -- stopping myself...
Command terminated by signal 6
        Command being timed: "octave"
    {{{ SNIP }}}
        Exit status: 0



    _______________________________________________________

Reply to this item at:

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

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