Praetorian <email@example.com> wrote in message <firstname.lastname@example.org>... > > I'm not so sure you can't use the mxMalloc and mxFree from within a > shared library. I modified the code so that I was calling the DLL's > allocate function followed immediately by the deallocate function; I > then called the mex file from the command line 1000 times and didn't > get any seg faults. The reason I got one yesterday was because I > allocated memory using the DLL in one call to the mex file and then > tried to deallocate it during the next call. But my tests from > yesterday show that the Matlab memory manager does garbage collection > on the memory allocated by the DLL when the calling mex file exits. So > the memory allocated in the first call had already been deallocated > (by the memory manager) and I tried to explicitly deallocate it in the > next call resulting in the segv. > > Ashish.
Ah, got it. Thanks! I put in a mexMakeMemoryPersistent call in the dll and now everything works ok. That puts the burdon of clearing the memory on the dll programmer, but that's really as it should be. I tested my example using both API calls from within a mex and from the MATLAB prompt using loadlibrary and calllib. Works in both cases, no memory leak and no memory corruption. The dll detects when it is being detached from MATLAB, so the programmer can put code in the dll to automatically clear the memory in that event.