From: Tom on
I just ran into the exact same problem. Were you able to solve this matter?

My code runs fine in Matlab but the compiled program crashes on that mllapack.dll message.

Quite frustrating...

Thanks,

Tom
From: Bruno Luong on
"Tom " <t_vanesch(a)yahoo.com> wrote in message <hqdi2m$rbo$1(a)fred.mathworks.com>...
> I just ran into the exact same problem. Were you able to solve this matter?
>
> My code runs fine in Matlab but the compiled program crashes on that mllapack.dll message.
>

I have encountered very similar problem under 2006B window (we still use this old version for our commercial product).

In my case:
- The issue seems to appear only at the very first call to a ML built_in matrix function
- nothing crashes as long as the result will not be used by the program

Based on that, I make a nasty workaround:
- After initialization of my application, call a dummy DLL compiled function that in turn call ML QR, for example.
- Then call my other DLLs as normal

So far it works, but the "solution" is unsatisfied. I agree it's a pain.

Bruno
From: Tom on
Thanks for the tip.
But when I include a dummy function, as below, I get the "crash"and "mllapack.dll" message when the main program calls this function in the compiled program.

>function DummyFunction()
> input=[4 5 6; 6 7 8; 10 2 5];
> test_out=svd(input);
>return;

Even when I compile this simple function as stand alone, it crashes too.

When I use the dependency walker, I see that it finds and loads the mllapack.dll but that it calls an unknown function...

Any other ideas or tips are welcome.
From: Tom on
I found that the error comes from a dll version problem (as suspected)

an older "libmmd.dll" was present in windows/system32 directory.

the version that comes with the Matalb Runtime bin/win32 directory was not used.

Getting rid of the older version solved the problem.

I haven't figured out yet why it was there and why it doesn't get updated in the windows directory when installing the vcredist.

What a pain.