I get an Access violation reading location when using mxCreateCh​arMatrixFr​omStrings

29 views (last 30 days)
I am using mxCreateCharMatrixFromStrings in a C++ console app. I have read in the 'string' from a .mat file into a char *cData[10] using mxArrayToString(). I can see the string in cData[0] and it is what I expected. I take that variable and then call the following in C++:
mxArray *pMatr = nullptr;
pMatr = mxCreateCharaMatrixFromStrings(345, (const char**)cData[0]); <-- this line is where I get the access violation error!
my goal is to have an pointer to an 1X344 mwArray to pass into a matlab generated library.
I am using MatLab R2014 as the matlab generated library needed to be 32 bit.

Accepted Answer

James Tursa
James Tursa on 11 Dec 2018
Edited: James Tursa on 11 Dec 2018
You should show the entire code you are using, not just a snippet of it. Also, the fact that you have a typo in the function name (which would have caused a LINK error) tells me that you typed this code in manually instead of copying and pasting it. Please don't do that! Just copy and paste the actual code.
That being said, I assume you have done something like this:
mxArray *pMatr = nullptr;
char *cData[10];
cData[0] = mxArrayToString( something );
pMatr = mxCreateCharMatrixFromStrings(345, (const char**)cData[0]);
The variable name cData does in fact reduce to type (char **) when used in an expression, so it is already of the correct type to simply pass in directly as the 2nd argument. And in fact that is precisely what mxCreateCharMatrixFromStrings is expecting. Also, the 345 will cause a seg fault since there are only 10 physical elements in the cData array. So it needs to be something like this:
mxArray *pMatr = nullptr;
char *cData[344];
cData[0] = mxArrayToString( something );
// other code here to assign cData[1], cData[2], ..., cData[343]
pMatr = mxCreateCharMatrixFromStrings(344, cData);
Also note that in R2016b and earlier, the allocated memory from the mxArrayToString( ) call is not on the garbage collection list. So you would have to manually mxFree( ) each individual cData element to avoid memory leaks.
  1 Comment
Edwardo Medina
Edwardo Medina on 11 Dec 2018
So by copying the whole code in I can guess that in trying to resolve the issue you are reproducing it locally from the submitted code. Good to know for the futrue.
thank you,

Sign in to comment.

More Answers (1)

Mohan Feng
Mohan Feng on 11 Dec 2018
It seems that in your code, cData[0] is of type char*, but you convert it into type char**, which may cause a segmentation fault.
James Tursa
James Tursa on 12 Dec 2018
I don't believe you. Passing in cData[0] as the 2nd argument couldn't possibly have worked, since that address points to a string of characters and is not the same as cData all by itself.

Sign in to comment.


Find more on Performance and Memory in Help Center and File Exchange

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by