Sherman,
I just noticed that what I had posted earlier only worked once and I could no longer do the debugging. What you state is what finally fixed it for me. The problem, as I understand it now, is when the osgviewer.exe (application) is built, the program database file overwrites the program database file that was created when the osgViewer.dll was built. Thus, when the application tries to load the symbols for the osgViewer.dll, it can't because it doesn't match - the osgviewer.pdb was generated from the osgviewer.exe build (and WinXP is not case-sensitive). So, to fix it, I deleted the osgviewer.pdb in the "bin\win32" directory and built the osgViewer project again (by deleting the .pdb file, it forced a rebuild on the osgviewer.dll without rebuilding all of the dependencies). If you select "Rebuild" from the interface, it will rebuild all of the dependent projects (e.g., core osg, core osgUtil, etc.). I didn't want to do that. Then, I started the osgviewer.exe application in debug mode. I get a warning that the symbols weren't loaded for the osgviewer.exe, but I didn't care. I'll investigate a way to set the project settings such that people don't have to use the workarounds. Hopefully, this can all be mitigated by some settings. chuck _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of sherman wilcox Sent: Thursday, February 08, 2007 12:35 PM To: osg users Subject: Re: [osg-users] Debugging VS7 This happens to me from time to time. Here's another thing to try, when you startup the debugger, look in the output window look for a line like so: 'osgvislib_driver_console.exe': Loaded 'C:\bsi\3rdparty\osg\OpenSceneGraph\bin\win32\osgTextd.dll', No symbols loaded. Notice the part that says "No symbols loaded". That line should read: 'osgvislib_driver_console.exe': Loaded 'C:\bsi\3rdparty\osg\OpenSceneGraph\bin\win32\osgTextd.dll', Symbols loaded. The fix, at least for me, is to re-compile the module in question. Just open OSG in Visual Studio and right click on the offending project and select "Project Only" => "Rebuild Only $PROJECTNAME" Another note, my path includes a reference to OpenSceneGraph\bin\win32 Let me know if that does the trick. If that fixes your problem as well, we should probably include this in the FAQ. On 2/8/07, Chuck Cole <[EMAIL PROTECTED]> wrote: Zach, In the project settings for Core osgViewer, change the C/C++ -> General -> 'Debug Information Format' setting to 'Program Database for Edit & Continue (/ZI)' (it is set to 'Program Database (/Zi)' by the CVS project file). This is how VS8 is setup and I believe VS7 is the same, but the exact names and menu options may be slightly different. After changing this setting, I was able to hit breakpoints within the osgViewer::Viewer class whereas previously I was unable to do so. Hopefully, this is your intent as well. chuck > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:osg-users- > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] On Behalf Of Zach Deedler > Sent: Wednesday, February 07, 2007 9:23 PM > To: 'osg users' > Subject: [osg-users] Debugging VS7 > > Anybody have a clue why I can't step into osgViewer::Viewer code in Visual > Studio 7 when debugging OSG CVS? Its driving me crazy! > > > Zach > > _______________________________________________ > osg-users mailing list > [email protected] > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ <http://www.openscenegraph.org/> _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
