What might cause a segmentation fault calling matGetVariable

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

[James Tursa]

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]

Please post the relevant part of the code. Most likely it contains a bug.