[Octave-bug-tracker] [bug #52080] Segmentation fault when calling clear all on classdef with local functions that cause parse error

[Dan Sebald]

Follow-up Comment #3, bug #52080 (project octave):

I'm using version/changeset

changeset 24054:8a6747c6db1a
Sun, 17 Sep 2017 22:16:14 -0400

on Linux.  With the --no-gui option, the behavior is an infinite loop or hung
program, no segmentation fault.

But to isolate the problem, it seems to be the function clear that is the
problem:


octave:1> obj = seg_fault
parse error near line 10 of file /home/sebald/matlab/bug_52080/seg_fault.m

  syntax error

>>>   1+
        ^

octave:1> help clear
[snip]
octave:2> clear -v
octave:3> clear -f
^C^CPress Control-C again to abort.
^Cfatal: caught signal Interrupt -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
error: ignoring const interrupt_exception& while preparing to exit


where the program hung after line 3.  My guess would be that the syntax error
causes a clean-up of function foo2, but the reference to it is probably not
removed from the symbol table.  Hence clearing the function list ends up
clearing foo2, which is no longer valid.

    _______________________________________________________

Reply to this item at:

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

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