What might cause a segmentation fault calling matGetVariable

4 次查看(过去 30 天)
I have a Matlab script which saves several parameters and a data array to a *.mat file. I then run a program compiled from c and c++ code using gcc (vs. 4.6.1). It reads the variables from the mat file, using the functions in mat.c. Several variables are read correctly, but it fails on some 2D arrays, with a segmentation fault. (Some 2D arrays, in a different file are read correctly.) I have traced the calling sequence to getMatVariable, and the calling stack from this library object ("no source available" to the debugger), ends with
_int_malloc() at 0x31fa67a258
malloc() at 0x31fa67ab1c
H5FL_reg_malloc() at 0x7ffff1f3ad1e
The behavior is the same with Matlab versions R2014b and R2015b.
Please advise, With thanks, Campbell
  2 个评论
James Tursa
James Tursa 2016-2-5
I assume you mean matGetVariable. How large is the variable? Do you have enough memory to load it? Is the function returning a NULL pointer?
Jan
Jan 2016-2-5
Please post the relevant part of the code. Most likely it contains a bug.

请先登录,再进行评论。

回答(0 个)

类别

Help CenterFile Exchange 中查找有关 MATLAB Compiler 的更多信息

产品

Community Treasure Hunt

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

Start Hunting!

Translated by