How to debug an external library (OpenCV) in Visual C++?

Question

I am developing a project in VC++2008. The project uses the OpenCV library (but I guess this applies to any other library). I am working with the Debug configuration, the li

Answer 1

Confirm: are you actually compiling the OpenCV library from source, or are you just linking against it?

A couple of possibilities come to mind:

It sounds like the debug info for the OpenCV library is not available (the PDB files). You may have to extend PATH to reference the directory containing these files. It seems to me that there is a way of doing this from VC++ but I'm a few years out from using the tool...

Is cvStererCalibrate also a "macro function"? If so, find out what real function it refers to and set the breakpoint in the library.

Finally, although you have already said so, it never hurts to go back and confirm that full debugging has been activated for everything in the project, including external libraries.

I don't know if this helps, but its a good place to start.

Answer 2

i got the same problems, which is:

'ccisample.exe': Loaded 'C:\OpenCV2.1\bin\cv210d.dll'

'ccisample.exe': Loaded 'C:\OpenCV2.1\bin\cxcore210d.dll'

I solved it by:

Linker -> Input -> Additional Dependencies add: 'cv210.lib; cxcore210.lib; highgui210.lib;'

instead of adding : 'cv210d.lib; cxcore210d.lib; highgui210d.lib;'

Answer 3

To sum up all the activity in the comments: the key to the solution was to rebuild the library in VC++ to obtain the .pdb (Program Debug Database) files for debugging, the precompiled "-d" suffix libraries weren't enough. Still, the import libs for the library dlls made the program load precompiled dlls from the OpenCV package tree, not the ones from my build with the .pdb information (the paths were similar so I didn't notice at first). The path to the .pdb files was provided in Tools|Options, but these files weren't loaded because of module version mismatch (obviously). Once I copied the correct dlls and their respective .pdb files to the application directory, the debugger started working inside the library functions.