[osg-users] more on Windows debugging
jss at cs.utexas.edu
Wed Sep 26 12:04:58 PDT 2007
I have the same problem. It is caused by using the debug dlls from the
install directory. If you setup your environment to find the dll files
in the directory in which they were built then everything works ok. My
guess is that the absolute path names to the source files are embedded
> Usually, VS will prompt you for a file location if it cannot find a file. It sounds like your DLLs are being loaded from the correct place, but just in case, make certain that the DLLs you just recently built match the ones that are being loaded. It's been my experience that PDB files can be very picky (frustatingly so, sometimes). Check your output window for the DLL names. Also, set a breakpoint on some code that calls an OSG function. Step into that code and see what happens. The IDE should prompt you for a source filename if it cannot determine where it is.
> That's all that I can think of at the moment.
> Hope it helps,
> On Mon Sep 24 10:39 , 'Andy Skinner' <Andy.Skinner at mathworks.com> sent:
>> Has anyone had to do anything tricky to see OSG source code while
>> debugging their application?
>> I've been able to compile OSG debug, and to put the .pdb files where
>> Visual Studio can see them. If I stop in my code, I can see OSG symbols
>> on the stack trace. But I can't see the source code.
>> I've added the directories I need to a list of debug source locations.
>> Does anyone else know how I should be able to see into the OSG source in
>> Visual Studio?
>> osg-users mailing list
>> osg-users at lists.openscenegraph.org
> osg-users mailing list
> osg-users at lists.openscenegraph.org
More information about the osg-users