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

[Sébastien Villemot]

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


[comment #1 commentaire #1 :]
> mexCallMATLAB returns a status code.  Are you checking that code to see if
an error happened during the function call?  Is that code correct in that when
it is 0, the return values are okay and when it is non-zero, the return values
are empty?

Yes, my code checks the return value of mexCallMATLAB. And when the problem
manifests (return values empty), that return code is 0.

I attach the minimal test case that I had constructed. The M-file function is
the same as in the context where the problem is encountered. The MEX file on
the other hand is much simplified. As I told before, the problem does not
manifest in this simplified test case, but that will give you a more precise
idea of the problem.


(file #50388, file #50389)
    _______________________________________________________

Additional Item Attachment:

File name: bug59597.c                     Size:0 KB
    <https://file.savannah.gnu.org/file/bug59597.c?file_id=50388>

File name: bug59597_fun.m                 Size:1 KB
    <https://file.savannah.gnu.org/file/bug59597_fun.m?file_id=50389>



    _______________________________________________________

Reply to this item at:

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

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