<p align=left>Since upgrading to VS2008 (from 2003) Ive experienced a bug where the development environment claims that there is no matching symbols for my main executable. The sequence of events is typically:
<p align=left>
<p align=left>1) Update my working copy from source control or make some of my own edits.
<p align=left>2) Build solution (debug or release, not a scratch build)
<p align=left>3) Attempt to start debugging
<p align=left>4) Get a message box that says "Debugging information for blah.exe cannot be found or does not match. No symbols loaded. Do you want to continue debugging?"
<p align=left>
<p align=left>Closing and reopening the development environment fixes the problem (a rebuild does not). I saw this once or twice before with vc2003 (over the course of 2-3 years), but now I see it almost daily with vc2008.
<p align=left>
<p align=left>My solution has around 80 projects in it, if that matters. We use pdb (/Zi) for our symbols.
<p align=left>
<p align=left>Clearly, if it were easily reproduced, I would report it to the Connect site, but it is not. Anyone from MS with some ideas on what would cause this? Perhaps we can work backwards and come up with a repo case?
<p align=left>
<p align=left>Thanks,
<p align=left>
<p align=left>
View the full article
<p align=left>
<p align=left>1) Update my working copy from source control or make some of my own edits.
<p align=left>2) Build solution (debug or release, not a scratch build)
<p align=left>3) Attempt to start debugging
<p align=left>4) Get a message box that says "Debugging information for blah.exe cannot be found or does not match. No symbols loaded. Do you want to continue debugging?"
<p align=left>
<p align=left>Closing and reopening the development environment fixes the problem (a rebuild does not). I saw this once or twice before with vc2003 (over the course of 2-3 years), but now I see it almost daily with vc2008.
<p align=left>
<p align=left>My solution has around 80 projects in it, if that matters. We use pdb (/Zi) for our symbols.
<p align=left>
<p align=left>Clearly, if it were easily reproduced, I would report it to the Connect site, but it is not. Anyone from MS with some ideas on what would cause this? Perhaps we can work backwards and come up with a repo case?
<p align=left>
<p align=left>Thanks,
<p align=left>
<p align=left>
View the full article