ansaurus

Question

Answer 1

+1 A:

A long time ago I had problems with Matlab <-> VS interop. It might be some microsoft visual c++ runtime library discrepancy. Check what runtime lib is required by matlab and what version does your visual studio have. I remember using Depends to get the dll dependencies for my program. Check your call stack after crashing (by attaching your msdev debugger) it might give you some hints.

It was a long time ago so I'm just giving hints of what I remember.

code-gijoe 2010-07-29 15:28:18

I haven't used Spy++ yet. I just made sure that the same compiler was used and that the same switches (/MD) was passed, which I though would be enough to have them use the same version.

Ben 2010-07-31 11:26:59

Sorry I said Spy++ it's actually Depends (Dependency walker). Check this out:http://msdn.microsoft.com/en-us/library/ms235265(VS.80).aspx

code-gijoe 2010-08-02 17:48:25

Check if it crashes inside a Matlab dll or inside a MS runtime dll (by attaching your debugger).

code-gijoe 2010-08-02 17:51:34

It crashes inside opencv_features2d211.dll when OpenCV tries to call vector::resize.

Ben 2010-08-03 08:19:35

Well, my best advice would be to compile OpenCV in debug so you can check why it's crashing. Have you tried giving the vector an initial size? Some big value.

code-gijoe 2010-08-03 13:46:38

Answer 2

A:

The data in a vector should still be stored as a single contiguous block

std::vector<int> data;
int *array = &data[0]; 
int *array = &data.front();

Should give you 'c' style pointers to the data, try passing these to matlab

see also: http://stackoverflow.com/questions/1062601/how-does-the-c-stl-vector-template-store-its-objects-in-the-visual-studio-compi

Martin Beckett 2010-07-29 15:32:37

You misunderstood my problem. The problem is not passing data to Matlab. It is the fact that the above code crashes.

Ben 2010-07-31 11:25:59

ansaurus

tags:

views:

answers:

OpenCV, Matlab and STL containers

related questions