[Octave-bug-tracker] [bug #52904] "mesh" with input array of "logical" causes error

[Dan Sebald]

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

Yes, this could be a case where the error is allowed to happen, i.e., in the
following:


octave:1> function [a] = badfunction()
>   this = isbad();
> end
octave:2> set(groot,"defaultaxescreatefcn", @badfunction);
octave:3> h = mesh(zeros(25));
error: 'isbad' undefined near line 2 column 10
execution error in graphics callback function
octave:4> h
h = -6.3352
octave:5> 


All seems well, except for the fact that the callback failed.

If more protection is required around those functions, it should probably be
one at a time rather than everything in a single try/catch.  Otherwise the
code will still be continuing on to use an incomplete graphics object, if only
for just another one or two internal functions...that use could be the source
of a segfault.  But, again, maybe the current patch is proper/acceptable.

    _______________________________________________________

Reply to this item at:

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

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