[Octave-bug-tracker] [bug #63388] Octave may crash with uitable containing true/false data

[Arun Giridhar]

Follow-up Comment #12, bug #63388 (project octave):

Take the code from comment #11 and change the subfunctions like this.
This works without any problems:

function parameters=opt_pso_parameters1(varargin); 
  ii=0; 
  ii=ii+1;parameters(ii).name='method';          
parameters(ii).value='foofoo';
  ii=ii+1;parameters(ii).name='plotFun' ;         parameters(ii).value=
'barbar';
  ii=ii+1;parameters(ii).name='flagVectorize' ;   parameters(ii).value=
false;
  ii=ii+1;parameters(ii).name='guessWeight';      parameters(ii).value=
int8(1);
endfunction

function parameters=opt_pso_parameters2(varargin); 
  ii=0; 
  ii=ii+1;parameters(ii).name='method';           parameters(ii).value='bar';
  ii=ii+1;parameters(ii).name='guessWeight';      parameters(ii).value= 1.5;
  ii=ii+1;parameters(ii).name='flagVectorize' ;   parameters(ii).value= true;
  ii=ii+1;parameters(ii).name='plotFun' ;         parameters(ii).value=
'foo';
endfunction


But this seemingly trivial change (changing the order of two parameters)
causes a crash:

function parameters=opt_pso_parameters1(varargin); 
  ii=0; 
  ii=ii+1;parameters(ii).name='method';          
parameters(ii).value='foofoo';
  ii=ii+1;parameters(ii).name='flagVectorize' ;   parameters(ii).value=
false;
  ii=ii+1;parameters(ii).name='plotFun' ;         parameters(ii).value=
'barbar';
  ii=ii+1;parameters(ii).name='guessWeight';      parameters(ii).value=
int8(1);
endfunction

function parameters=opt_pso_parameters2(varargin); 
  ii=0; 
  ii=ii+1;parameters(ii).name='method';           parameters(ii).value='bar';
  ii=ii+1;parameters(ii).name='guessWeight';      parameters(ii).value= 1.5;
  ii=ii+1;parameters(ii).name='flagVectorize' ;   parameters(ii).value= true;
  ii=ii+1;parameters(ii).name='plotFun' ;         parameters(ii).value=
'foo';
endfunction


So an extra clue is that if a parameter changes data type from boolean to
something
else or vice versa, it causes a crash. If parameter #3 (say) in all the
different cases stays boolean, then it doesn't cause a crash. In other words:
constructing and destroying that checkbox to show a boolean is causing an
error.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63388>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/