Occasionally, the debugging session will abruptly ended, leaving me just this window:
Apparently there was an exception happened, and that’s how the 32-bit debugger handles it. Sucks right?
So in order to get the Exception details, you just need to put one single try-catch to cover the whole application, and put a breakpoint inside the catch section.
By now, you should be able to get the exception details whenever you x86 debugging session abruptly ended.
GD Star Rating
loading...
Visual Studio 2008 Error: vshost32 has stopped working, loading...
About Hardono
Hi, I'm Hardono. I am working as a Software Developer. I am working mostly in Windows, dealing with .NET, conversing in C#. But I know a bit of Linux, mainly because I need to keep this blog operational. I've been working in Logistics/Transport industry for more than 9 years.
Incoming Search
vshost32 has stopped working
Thanks for the tips, Mate!