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

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

Active

Type:	Bug
ID:	559805
Opened:	5/18/2010 5:47:38 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

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 (expand)

English

Visual Studio 2010

Windows 7

English

1: Create a simple application that causes a stack overflow (infinite recursion) exception

2: Set the post build step in VS to the following:

cmd /c svnindex.cmd /debug /source=$(SolutionDir) /symbols=$(TargetDir)
symstore add /r /f $(TargetDir)\*.* /s c:\symbols /t $(ProjectName) /v "Build Number"

3: Check the solution into SVN and compile through standard mechanism

4: Run the solution by double clicking the executable (not through VS so it runs the standard projectname.exe binary and NOT the projectname.vshost.exe binary) I'm not sure whether this really matters though.

5: Debug the error using a new instance of visual studio

6: Take a crash dump of the process

7: Close all visual studio instances

8: Rename the visual studio folder so the debugger can't find it

9: Open the crash dump in visual studio, click "debug with mixed" option

At this point I see a bunch of output in the command window of it resolving symbols and/or downloading them. Visual studio then hangs for seemingly infinite time (I let it run for a few hours) pegging a single CPU core. It eventually crashes with an error (The instruction at 0x572fe52e referenced memory at 0x00000000. The memory could not be read).

I see a bunch of output in the command window of it resolving symbols and/or downloading them. Visual studio then hangs for a long time time (I let it run for a few hours) pegging a single CPU core. It eventually crashes with an error (The instruction at 0x572fe52e referenced memory at 0x00000000. The memory could not be read).

Ideally it would 1) locate the binaries in my symbol store, 2) locate the PDB files from the symbol store and load them for the binaries 3) use the symbol information to extract source code so I could repro issues easily from just a minidump.

0 attachments

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)