[Octave-bug-tracker] [bug #46559] Crash with mexErrMsgTxt

[Guillaume]

URL:
  <http://savannah.gnu.org/bugs/?46559>

                 Summary: Crash with mexErrMsgTxt
                 Project: GNU Octave
            Submitted by: gyom
            Submitted on: Fri 27 Nov 2015 17:26:49 GMT
                Category: Libraries
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Crash
                  Status: None
             Assigned to: None
         Originator Name: Guillaume
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

On recent builds, I observe that Octave freezes or crashes when an error is
triggered within a MEX file. If you run the code below without any input
argument, it returns an error as expected but if you call it with a numeric
value, Octave crashes:

++
#include "mex.h"

void mexFunction(int nlhs, mxArray *plhs[], int nrhs, const mxArray *prhs[])
{
    if (nrhs != 1)
        mexErrMsgTxt("One input argument.");
    if (!mxIsChar(prhs[0])) {
        mexErrMsgTxt("Input must be a string.");
    }
}
--




    _______________________________________________________

Reply to this item at:

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

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