Home Dashboard Directory Help

pdbcopy tool that comes with SDK only works on x32 platforms by Chris P Johnson


 as Fixed Help for as Fixed

Sign in
to vote
Type: Bug
ID: 728802
Opened: 3/5/2012 6:47:23 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
User(s) can reproduce this bug


I couldn't find any better product to post this bug against. Please reassign it if needed.

This issue was raised before, and still was not addressed:

When I attempt to strip PDB's, the tool pdbcopy.exe that comes with the windows debugging toolkit always fails with:
"Can't load dll mspdb80.dll"
Now my computer running Win7 x64 has exactly 5 different versions of mspdb80.dll on it. When I put all the directories containing those DLL's on the PATH environment variable, I get error messages stating that it can't get the address of a procedure.

My colleques state that it does work however for 32 bit operating systems.

So I tried to install the 32 bit version of the windows debugging toolkit only to find that I can't. The installer WILL NOT install the 32 bit version of the windows debugging toolkit on an x64 system. It installs 64 bit platform tools only.... :(
Sign in to post a comment.
Posted by Chris P Johnson on 3/7/2012 at 4:36 PM
Good to hear. Can't wait.
Thanks so much for the response.
Posted by Microsoft on 3/7/2012 at 4:11 PM
The problem will be fixed in a future release of SDK tools in Windows debuggers. We have made pdbcopy.exe only depending on system DLLs.

Thanks for your feedback.

YongKang Zhu
VC++ CodeGen and Tools
Posted by MS-Moderator07 [Feedback Moderator] on 3/5/2012 at 11:28 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by MS-Moderator01 on 3/5/2012 at 7:08 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.