Question Locked

No symbols are loaded for any call stack frame.

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Several months ago I bought and installed Visual Studio 2005 Pro.

Everything worked perfectly and I was a happy camper.

Now, all of a sudden, when I try to step through any program I get a dialog box that states:
"No symbols are loaded for any call stack frame. The source code cannot be displayed."

I have googled this thing to death and found no real answers that I can use.

However, if I close the dialog box and click on Debug/Windows/Threads and then freeze one of the "inactive" threads I am then able to step throught the program. The only problem is that stepping is now VERY slow. It takes about 10 times as long as it normally does.

This problem seems to have started about the time that I installed .NET 3.0 Framework. Could this be the problem?

This is very frustrating as I am just now learning VS 2005 and VB.NET.

Any help would be appreciated.

3 replies

by juanma_ar83

Hello Mark,
I have the same problem. I'll add a new report when appear this dialog box after appear this.
ContextSwitchDeadlock was detected

The CLR has been unable to transition from COM context 0x1c37f0 to COM context 0x1c3960 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long runnning operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.

And Troubleshooting tips:
Get information about MDAs.

by daveherron

THE FIX: From Debug->Exceptions->Managed Debugging Assistants, make sure the "ContextSwitchDeadlock" and "LoaderLock" exceptions are not thrown by unchecking their check-boxes. (If you don't see "Exceptions" in the Debug menu, add it through Tools->Customize->Commands->Debug. Drag and drop "Exceptions" to the "Debug" menu.)

This discussion is closed to new replies.