Visual Studio 2012 - Source Not Available After Pressing Pause While Debugging

Question

Hi,
In Visual Studio 2008, when we'd open a dialog in our application (Native C++, 64-bit) and pressed 'Pause', the debugger would automatically go to the location of the dialog in the code and the call stack would show the series of calls to arrive
at the current position.
Now that we've upgraded to Visual Studio 2012, this functionality is lost.  When we press 'Pause', a 'Source Not Available' tab will appear.  The call stack shows the following:
ntdll.dll!ZwWaitForSingleObject()
KernalBase.dll!WaitForSingleObjectEx()
<several lines of nvoglv64.dll>
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
At first we thought it was a symbol issue since none of the Windows-related dlls had pdbs. None of our workstations are connected to the Internet so I used symchk to download all the required symbols.  Despite all of the symbols now being loaded, the
debugger still doesn't show the actual call stack into our code.
Is there a setting somewhere that needs to be set? Or are we out of luck since our machines are never online?
Any thoughts are apprecated.
Thanks.
Visual Studio Premium 2012 (11.0.60610.01 Update 3)

Answer 1

Hi,
Welcome to MSDN.
In Visual Studio 2008, when we'd open a dialog in our application (Native C++, 64-bit) and pressed 'Pause', the debugger would automatically go to the location
of the dialog in the code and the call stack would show the series of calls to arrive at the current position.
Now that we've upgraded to Visual Studio 2012, this functionality is lost.  When we press 'Pause', a 'Source Not Available' tab will appear.  The
call stack shows the following:
ntdll.dll!ZwWaitForSingleObject()
KernalBase.dll!WaitForSingleObjectEx()
<several lines of nvoglv64.dll>
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
According to these words above, do you mean clicking “Break All” as following image?
The error means that our project does not contain source code for the code that we are trying to view, you could refer to
this link for more information.
In order to solve this issue, you could debug it in another machine which can download symbols form Symbol Servers, then copy that
symbols to your machine to test.
You could change the Symbols setting of the Visual Studio of the other machine as following image:
Then copy the symbols in that directory to your machine, and change the Symbols settings to your local directory to test.
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.