在64位Windows 7上使用mingw-w64在C / C ++中通过engOpen调用MATLAB时崩溃

Question

I am trying to figure out why my C/C++ program crashes when I call MATLAB's engine with engOpen() . The code below prints Hello World and then throws an APPCRASH .

What might be causing this crash, or how do I debug from here?

testMATLAB.c

#include <stdio.h>
#include "engine.h"

int main(){
printf("Hello World.\n");
    Engine *ep;
        if (!(ep = engOpen(NULL))) {
            printf("Can't start MATLAB engine\n");
        } else {
            printf("Opening Matlab Engine\n");
        }

return 0;
}

More Details

I am using:

• MATLAB R2012a
• mingw-w64 gcc version 4.8.0
• 64 bit Windows 7

In response to a number of existing SO Q&As, I have

• confirmed that I am linking to C:\\Program Files\\MATLAB\\R2012a\\extern\\lib\\win64\\microsoft\\libeng.lib and C:\\Program Files\\MATLAB\\R2012a\\extern\\lib\\win64\\microsoft\\libmx.lib .
• included C:\\Program Files\\MATLAB\\R2012a\\bin\\win64 in my path which contains libengine.dll and libmx.dll
• ran matlab /regserver from the windows command prompt

Note, if I place the engOpen() inside an if statement that isn't executed, then the code runs to completion.

I also do not think this is inherent to mingw because on a 32 bit WinXP machine I had no problem using MATLAB 2011 with mingw32 .

Compiler and linker output is at http://pastebin.com/z9CAsb6X

Answer 1

How did you link the *.lib? On my project I use PostgreSQL and instead of linking the provided MSVC-compiled *.lib I had to convert it to *.a. I think it was a procedure like this one:

http://oldwiki.mingw.org/index.php/CreateImportLibraries

Answer 2

I link using those DLL directly rather than lib files, say: libeng.dll, libut.dll, libmex.dll and libmat.dll .

My setup is MinGW 4.8.1 64bit, Win7 64bit, Matlab 64bit .

It works for me.

Answer 3

I had a similar problem using Visual Studio. I think it has to do with the way Matlab 64 bit handles warnings after it closes. I had to add: (Mathworks solved my problem there)

warning('off','MATLAB:ClassInstanceExists') % Add this line

to my matlab code, which probably meant there was some matlab class that was not really needed in my code, but still matlab compiler wanted to find? (my guess...)

If this does not work directly you might want to disable more warnings?...