4
Practically every time I try observe the contents of a variable or property of an object, I get the error below:
Function Evaluation disabled because a Previous Function Evaluation timed out. You must continue Execution to reenable Function Evaluation.
This did not happen on VS210 or VS2012, at least not until the last patch of updates.
The question is. Is there any configuration, or application setting for the Debugger Watcher to work correctly again?
2
I had the opportunity to try this warning on VS2010 as well. In fact, it may appear whenever the content you are inspecting takes too long to suffer Eval.
For the purpose of debugging, Eval equivalent to the sequestration of the thread observed by Debugger, which then allows you not only to access the thread content but also to manipulate it (for example by running code directly in Debug CLI).
The main problem with this technique is that in order to freeze the state of the application, the Debugger stops all other threads. The obvious problem occurs if the observed thread tries to interact with any of the frozen threads.
If this is your case, the resolution of your problem will depend on the way your code has been implemented.
Browser other questions tagged visual-studio-2013 visual-studio debug
You are not signed in. Login or sign up in order to post.
Makes sense now. Since it usually occurs in an asynchronous code snippet.
– Alan R. Soares
Exactly. This can also happen if one of the frozen threads is consuming an object in Synclock, and the main thread tries to do it during debugging.
– OnoSendai