为什么Visual Studio在调试时停止？

Question

Sometimes, while I am debugging ac# application, I will hit a break point and when I try to continue, step or step into, it just does nothing. The yellow line highlighting the current line goes away, but it never reaches the next line. The app is still frozen like I am on a breakpoint and I can do nothing but hit the stop debugging button and restart. This doesn't happen all the time, but once it starts on an app it seems like it always happens after that for that app. I have found that adding the following code just before the class declaration "fixes" the problem for that app, but am very curious as to why this is happening.

[System.Diagnostics.DebuggerDisplay("Form1")]

Additional details: I have not noticed any kind of pattern as to what the particular line does when it freezes. Most of the apps I write use threading, so there is a decent chance this is happening within a thread every time.

Answer 1

I've seen stalling problems where the debugger is trying to evaluate the variables shown in the Auto/Local windows. If the evaluation is complicated then it can cause significant stalls.

You can turn the auto-evaluation off through Tools|Options and it does make a big difference.

Answer 2

I have come across with this kind of behavior, though this is my first time.

I have got through this problem, by two ways

1. Your way of putting this attribute, [System.Diagnostics.DebuggerDisplay("Form1")]
2. Turning off Tools->Options->Debugging->General->Enable Property evaluation and other implicit function calls.

I am still debugging my code but It seems to me that some of the Autos evaluation is failing (possibly throwing an exception), which is possibly crashing the debugger.

Please let us know if this is also your case.

Answer 3

What sort of code are you debugging?

When you "step into" are you calling your own .NET code, or calling a native library, or an external assembly that you don't have the pdb files for? Either of these situations would cause the debugger to freeze while the external code was executing.

Answer 4

If you debug multithreaded application you might be changing of thread. You can switch between Thread with the "Thread windows" while debugging to be able to see again where the debug yellow line is.

Answer 5

My psychic debugger says that you're missing symbols for something and that VS is hitting the network trying to look them up. Try setting your symbol path to something weird like C:\\foo.

Answer 6

dead-lock seems likely in your case. Press the pause button and look at the threads view next time it happens.

Answer 7

当我的数据库非常慢时，我已经看到了这种行为，NHibernate试图在引擎盖下写入它，并且整个调试器在数据库被挂钩时被随机锁定。