Symbols for Windows x64 debug under Visual Studio 2010?

asked 2012-11-18 17:35:02 -0600

SeeVee
1 ●1 ●2 ●3

updated 2013-04-16 14:13:33 -0600

20029 ●16 ●82 ●207 http://stevenputtemans...

For OpenCV 2.4.2, running under 64-bit Windows 7 (x64), I want to use the Visual Studio 2010 debugger to step through cv::calcHist(). I have downloaded the source code, but for the debugger to work, it needs the symbol file (.pdb). How can I get the appropriate symbol files?

The linker has C:\Program Files\OpenCV\build\x64\vc10\lib and C:\Program Files\OpenCV\build\x64\vc10\bin 
as Linker / General / Additional Library Directories, and opencv_highgui242d.lib, opencv_core242d.lib, 
opencv_imgproc242d.lib, opencv_ml242d.lib and opencv_video242d.lib as Linker / Input / 
Additional Dependencies.

edit retag flag offensive close merge delete

add a comment

answered 2012-11-19 01:56:28 -0600

Daniil Osokin

2197 ●5 ●32

updated 2012-11-19 01:58:12 -0600

Hi! You can build OpenCV in VS from source code to get the symbol file. Build process explained in installation guide.

edit flag offensive delete link

Comments

I see these instructions. This looks like a good solid week of work, figuring out how to install all the libraries, and getting over the minor roadblocks which always come up during sw installation. Since someone already built the libraries and DLLs for 64-bit Windows 7, I was hoping they had also built the corresponding symbol files.

SeeVee ( 2012-11-19 11:41:21 -0600 )edit

This can be done in a couple of minutes. You just need to download OpenCV source, configure it with CMake and build in your IDE. It's trivial. Other libs (3rd party) - just for some features. If you don't need them - do not install them (skip 6th step in installation guide) .

Daniil Osokin ( 2012-11-20 02:41:22 -0600 )edit

I followed the instructions, but when I try to build, I get many of these: fatal error LNK1104: cannot open file '....\lib\Debug\opencv_core240d.lib'

paj006 ( 2012-11-26 14:06:54 -0600 )edit

@paj006 What instructions (Installation guide)? I'm think this should be a new question.

Daniil Osokin ( 2012-11-28 02:25:40 -0600 )edit

If you make debug DLLs available, you should make PDB files available. That's best practice. Otherwise, you're requiring your users to build, which they were trying to get around by downloading your pre-built libraries in the first place.

It's not hard. It's helpful to us. Why do you balk?

mcow ( 2013-04-16 13:44:19 -0600 )edit

Mr Mcow, a bit of respect is in its place right? First of all be happy that the provided functionality is actually there, if you do not like it, use another computer vision library. Secondly, it is plain and simple why prebuilt binaries don't contain pdb files, namely that people just take the functions as is. Given the correct input, the output is assured. If you want any more, then be patient and compile the system yourself, it only takes once to figure it out! Be friendly or your posts will just get deleted.

StevenPuttemans ( 2013-04-16 16:42:12 -0600 )edit

@StevenPuttemans: My comment was not disrespectful. Your "it is plain and simple why prebuilt binaries don't contain pdb files, namely that people just take the functions as is" is an example of the correct meaning of "begging the question."

mcow ( 2013-11-22 13:10:25 -0600 )edit

add a comment

Symbols for Windows x64 debug under Visual Studio 2010?

1 answer

Comments

Links

Question Tools

Stats

Related questions

Symbols for Windows x64 debug under Visual Studio 2010? edit

1 answer

Comments

Links

Question Tools

Stats

Related questions

Symbols for Windows x64 debug under Visual Studio 2010?