[Octave-bug-tracker] [bug #59597] bogus result returned by mexCallMATLAB

[Sébastien Villemot]

Follow-up Comment #9, bug #59597 (project octave):


[comment #7 commentaire #7 :]
> Question #1: Is there any variability about when the mex file fails?  For
example, does it occasionally fail on the second invocation or occasionally on
the fourth invocation or is it always *exactly* the third?

It consistently fails exactly on the third time whenever I run it manually.
However I’ve not tried to execute it a large number of times to verify this
more systematically.

> Question #2: Can you try putting a keyboard command at the bottom of the
m-file.  Then call your code normally.  When the interpreter stops in the
m-file, inspect the variables to see if there is any thing wrong with them at
the interpreter level.

I did, and the variables look correct just before returning from the function
in the m-file.

> Question #3: In the mex file, could you add this line to the start of the
function?
> 
> 
>   mexSetTrapFlag (0);
> 
> 
> This should ensure that if something goes wrong with the call to feval()
that an error is thrown.

I did, and it changes nothing.


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via Savannah
  https://savannah.gnu.org/