[Octave-bug-tracker] [bug #46536] bad indexing produces different error message in dev than default

[Rik]

Follow-up Comment #4, bug #46536 (project octave):

I reviewed your patch and have attached an updated version to the report.  jwe
has a specific style he likes in the commit messages so you can see the format
I used there.  The only other change was the variable name 'ex' to 'expr'
because that was the common name used elsewhere in the code.  It seemed
worthwhile to go with that convention since 'ex' could potentially also mean
exception and there was an exception input to the function.

One thing is not perfect, however, I now get a segfault for the following
sample code.


octave:1> x.foo.bar.baz = 1;
octave:2> x.foo.bar.baz(2)
panic: Segmentation fault -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
Segmentation fault




(file #35575)
    _______________________________________________________

Additional Item Attachment:

File name: bug_46536.v2.cset              Size:13 KB


    _______________________________________________________

Reply to this item at:

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

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