I am definitely using the dlls associated with the pdb files, which were generated in debug mode. I can find where the libraries come from, where the pdb files come from, etc, and all is in place. The symbols are in the stack trace as well. Before I was using debug directories, it couldn't tell me where it was in OSG.
One possible issue is that these dlls have been copied to other places since they were built, and they're not in the same place relative to the pdb files or source code. But they are the files built with the pdb files and source code. It has been suggested that I try to load the OSG solution and attach to my program. This may now make it harder to debug our code, but it would be something. andy -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Sokolowsky Sent: Tuesday, September 25, 2007 5:16 PM To: OpenSceneGraph Users Subject: Re: [osg-users] more on Windows debugging Andy Skinner wrote: > I can step into header files, but not the source. I wonder why that is. > > It seems I'm pretty close, since it is finding the header file. If > anyone could suggest why Visual Studio can find one and not the other, > I'd be grateful. I've added both to the list of debug source. It sounds like there is no debugging information in the source files, especially if you're trying to step into the OSG sources which are located inside a library file. Header files are compiled into your program's sources so you can step into the functions contained therein. Are you using a debug version of the library? Eric _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.or g _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
