C Mex crashes if array is too large
显示 更早的评论
Hi all,
I am passing an array to a mex file as follows:
float *var;
var = (float*)mxGetPr(prhs[0]);
The mex file compiles/work perfect when the input is "small" (a few GB for my application), but when the input is larger, it crashes and gives me a segmentation fault. The input is held in memory (loaded into matlab workspace), and furthermore, the mex file shouldn't make a copy of the array (I'm just pointing to the array which is already in memory). Not only that, but I only need to access few elements of the input array at a time.
Any ideas on what could be causing this behavior?
One obvious candidate: I'm not compiling with -largeArrayDims (didn't update my code for 64-bit API). Might this be an issue?
3 个评论
James Tursa
2016-4-4
编辑:James Tursa
2016-4-4
We would need to see your code. -largeArrayDims could be an issue depending on what you are doing. Or it could be something else. Can't say without seeing your code. Side note, mxGetData is the preferred way of getting a (float *) to the data area:
var = (float *) mxGetData(prhs[0]);
JohnDapper
2016-4-5
James Tursa
2016-4-5
编辑:James Tursa
2016-4-5
Likely. -largeArrayDims controls whether mwSize is an int or a size_t. If you were using an int for the index and it wrapped around to a negative value then of course you would be pointing to invalid memory hence a crash. Keep in mind, however, that since mwSize is now likely a size_t in your code you need to be careful how you are doing your if-testing since size_t is unsigned. Are you actually "casting" an int to a size_t? I assume you meant typing the variable as a mwSize, not casting.
回答(1 个)
Dave Behera
2016-4-5
0 个投票
I think you should definitely try recompiling with -largeArrayDims. Also, paste a snippet of your code here.
类别
在 帮助中心 和 File Exchange 中查找有关 Performance and Memory 的更多信息
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!