Debugging information for '.exe' cannot be found or does not match. - by Yannick Letourneau

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


15
0
Sign in
to vote
ID 486244 Comments
Status Closed Workarounds
Type Bug Repros 16
Opened 8/28/2009 8:22:59 AM
Access Restriction Public

Description

When we launch a debug session, we are sometimes getting an error "Debugging information for '.exe' cannot be found or does not match.".  This happens very often, even after clean rebuilds of a solution.

Since our team upgraded to Visual Studio 2008, we are getting this error very frequently (some programmers on a daily basis, some even have 100% repro on some specific solution configuration).

Some people have been able to workaround this issue by killing the devenv.exe and mspdbsrv.exe process and restarting Visual Studio, but this workaround doesn't work for everyone and it affects productivity a lot as it can happen multiple times on a daily basis.
Sign in to post a comment.
Posted by Chris2561 on 10/20/2010 at 8:14 AM
I had a problem with Visual Studio described in http://support.microsoft.com/kb/2001115. I followed the advice and re-installed Visual Studio 2008 SP1. That resolved the issue. But then after that, I started having the issue described in this bug report.
Posted by Sean [MSFT] on 9/10/2009 at 9:45 AM
Thanks again for reporting this issue. Unfortunately, without a project to reproduce this issue we cannot investigate it further. If you have a chance to add a repro project to this issue, feel free to re-activate it.

Thanks!
-Sean Laberee
VS Platform Team
Posted by Sean [MSFT] on 8/31/2009 at 8:03 AM
Thank you for reporting this issue. This appears to be similar to an issue that we have seen on the forums but haven't reproduced internally. You can validate that you settings are correct by following the instructions in this forum post(http://social.msdn.microsoft.com/Forums/en-US/Vsexpressvc/thread/503d3ded-976e-460e-b5f9-7e03454ed387). However, if you could send us a sample project that reproduces the issue that would be appreciated.

Thanks!
-Sean Laberee
VS Platform Team
Posted by Microsoft on 8/31/2009 at 12:28 AM
Thanks for your feedback. We are routing this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team