Home Dashboard Directory Help
Search

Using Source Server tagged PDB's Causes VS 2010 to hang and crash by Cadieu


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 559805
Opened: 5/18/2010 5:47:38 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I'm trying to experiment getting source server support working in visual studio 2010. It seems to cause VS to hang when loading symbols.

I have checked the standard options in VS. Enable source server support is on, with outputting debug messages to the output window. It downloads the microsoft symbols and loads them fine. I verified with srctool.exe that the PDB files are able to extract the relevant files fine. I've also verified that the symbol files get stored in the symbol server path correctly. I tried running VS with debug information but there doesn't appear to be anything useful in log.

I'm at a loss of where to go from here. I wonder whether the binary search path needs to be set? If I don't rename where the project is, but just delete the files from the folder, it doesn't seem to make a difference in the behavior though. I couldn't find documentation on the binary search path for VS2010 although the windbg docs have some cryptic information on using this.

I think I gave enough to generate a repro case, but I could try to supply the actual files if necessary. I can reproduce this on both xp64 and Win7 32 bit
Details
Sign in to post a comment.
Posted by Microsoft on 12/17/2010 at 11:48 AM
Hello Cadieu,

Thank you for reporting this issue. I'm pleased to tell you that we were able to fix this issue and the fix is currently available as part of the VS 2010 SP1 Beta(http://www.microsoft.com/downloads/en/details.aspx?FamilyID=11ea69cb-cf12-4842-a3d7-b32a1e5642e2&displaylang=en)

Please try out that release and feel free to reactivate this issue if you don't believe the issue has been fixed.

Marc Paine
Visual Studio Debugger
Posted by Microsoft on 5/24/2010 at 2:46 AM
Thank you for reporting the issue.
We are routing 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 Microsoft on 5/18/2010 at 5:01 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.