[Octave-bug-tracker] [bug #48665] calling continue in a function outside of a conditional or loop silences stdout, may crash Octave

[Mike Miller]

Follow-up Comment #5, bug #48665 (project octave):

The segfault here is due to the changes to how errors are handled and
propagated. Whatever is happening with the "continue" in a user function, it
is also preventing the error() function from behaving properly inside user
functions. Since print_usage doesn't throw an error, the builtin function
"all" with no arguments continues running as if it had valid args, and
dereferences a bad pointer.

Observe



>> function foo, continue, endfunction;
>> foo
>> lasterr
ans = 
>> error asdfasdfasdf;
error: asdfasdfasdf
>> lasterr
ans = asdfasdfasdf
>> lasterror reset;
>> 
>> print_usage ("all")
>> lasterr
ans = 



In 4.0 and earlier versions, we always followed print_usage with a return
statement, so even if the error message was suppressed and the error state not
correctly recorded, the builtin function still returned control early.

    _______________________________________________________

Reply to this item at:

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

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