Hello
That errorcito scrub it, do not know if they ever came out but I did lose several hours, before wandering into what it means for truth is an issue I comment a bit thick "solution"
must turn off a checkbox that corresponds to MDA (managed debugging assistant) of ContextSwitchDeadLock name.
Debug / Exceptions / Managed debuging assistants.
Turn off the check box corresponding ContextSwitchDeadLock
By default option does not appear in the submenu Debug Exceptions, if that is the case añadanlo by:
Go to View / Toolbars / Customize
Once therein the left pane and select Debug from the options on the right will be exceptions, take the option and drag to the debug menu
Well now a small & # 241; to explain this, is that the MDA are assistants and aids used in the debug in coordination with the CLR, they generate informational messages run-time events and from what I understand the error that occurs in this case is that the debugger throws this exception and finding threads in the Implementation n being debugged that appear to be hung and not return any message, and the MDA, not knowing the state generates this exception. On the other hand I read it a problem in a COM component that the application is doing burreras hehe Early · Solutions · put them in quotes because if you actually realize the problem is not solved but if it prevents the Debug throw the error, the problem is most likely due to a COM component that is not communicating properly with the MDA and thus it throws the exception. Well
finally here's a few links in case you want to read more about this error, which is a rarity and if anyone thinks confused over this and wants to leave me a comment, will be welcome
http://msdn.microsoft.com/es-es/library/d21c150d (VS.80). aspx
http://msdn.microsoft.com/es-es/library/ms172233 (VS.80 ). aspx
Salu2
SergioT
0 comments:
Post a Comment