Home Dashboard Directory Help
Search

Source information stripped from PDB files for msvcr90.dll and msvcr90d.dll by wva


Status: 

Closed
 as Fixed Help for as Fixed


2
0
Sign in
to vote
Type: Bug
ID: 374834
Opened: 10/10/2008 5:25:18 PM
Access Restriction: Public
0
Workaround(s)
view
4
User(s) can reproduce this bug

Description

It is impossible to debug C runtime dlls on source level, because PDBs downloaded from Microsoft symbol server do not contain source information (i.e they are stripped).

If a program links statically to C runtime, debugging is possible.
in VS2005 debugging C runtime DLLs is also possible.
Details
Sign in to post a comment.
Posted by Jon Baggott on 10/29/2008 at 1:04 PM
The suggestion to add the path to local copies of the symbols to the symbol path does not work reliably because of the design (IMHO a poor one) of Visual Studio. See 251524 for details.
Posted by Microsoft on 10/27/2008 at 4:07 PM
Hello,

This an issue that we are currently working on the remedy for. We have asked the symbol server managers to deploy private symbols to the public internet symbol server for VC 7.0 RTM, 7.1 RTM, 7.1 SP1, 8.0 RTM, 8.0 SP1 and 9.0 RTM, as well as 9.1 SP1. Once these are deployed the symbols on the symbol server should contain the info necessary for debugging.

However, you can also get better behavior by making sure that your local copies of the symbols are first on your symbol path (previous to the symbol server versions).

Pat Brenner
Visual C++ Libraries Development
Posted by Microsoft on 10/27/2008 at 4:00 PM
Hello,

Thanks for the report. This is a problem that we are currently working on. We have asked the symbol server managers to deploy private symbols to the public internet symbol server for VC 7.0 RTM, 7.1 RTM, 7.1 SP1, 8.0 RTM, 8.0 SP1 and 9.0 RTM, as well as 9.0 SP1. So once this is complete, the symbols will work better for those official releases.

However, you can also get better behavior if you make sure that your symbol path (in your debugger) has the local Visual Studio installed symbols first in the symbol path (before the symbol server) so your local symbols are loaded instead.

Pat Brenner
Visual C++ Libraries Development
Posted by Microsoft on 10/13/2008 at 8:50 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com/)
Sign in to post a workaround.