[Octave-bug-tracker] [bug #50014] Octave segmentation violation when duplicate nested functions exist

[John W. Eaton]

Follow-up Comment #11, bug #50014 (project octave):

I added some additional tests (pushed to savannah).

My current iteration on a fix for the bug is attached here.  It is technically
a modification of a public interface because it changes the data type of a
public data member (base_parser::function_scopes).  So, should this only go on
default, or is it OK for stable?  I doubt that anyone is using this data
member directly, but I don't know if the change will cause trouble for other
things.  Our goal is to allow .oct files compiled for 4.0.0 to be used with
any 4.0.x Octave binary, but maybe this fix is more important than that?  I
don't know.

Although the final fix is relatively small and straightforward, it took me a
long time to get there and I'm still not really satisfied that it is the best
fix, but it seems to work.

(file #39474)
    _______________________________________________________

Additional Item Attachment:

File name: diffs.txt                      Size:7 KB


    _______________________________________________________

Reply to this item at:

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

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