Hello. I am developing a custom class library in visual stuido 2005 profesional eddition. There are some bugs in my code and I am trying to use the step debugger to walk through the code and examine the data. However at random points in the code the debugger will just stop and exit out. It happens in lots of differnt places through the code, not just one specific part.

If i keep clicking, "step into" fairly quickly, it will step through just fine. But if I pause for a minute to examine some data in the watch window, then 90% of the time the debugger will crash without any error message.

After the crash occurs, the following text appears in the debug output window.

bling, is the name of the test program i am running.

'bling.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'bling.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'bling.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'bling.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'bling.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Drawing\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'bling.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities.Sync\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'bling.vshost.exe' (Managed): Loaded 'C:\Documents and Settings\estubbs\My Documents\Visual Studio 2005\Projects\ccd.sitemap\bling\bin\x86\Debug\bling.vshost.exe', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'bling.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'bling.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The thread 0x934 has exited with code 0 (0x0).
The thread 0x8dc has exited with code 0 (0x0).
'bling.vshost.exe' (Managed): Loaded 'C:\Documents and Settings\estubbs\My Documents\Visual Studio 2005\Projects\ccd.sitemap\bling\bin\x86\Debug\bling.exe', Symbols loaded.
'bling.vshost.exe' (Managed): Loaded 'C:\Documents and Settings\estubbs\My Documents\Visual Studio 2005\Projects\ccd.sitemap\bling\bin\x86\Debug\ccd.sitemap.dll', Symbols loaded.
'bling.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'bling.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'bling.vshost.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The program '[1736] bling.vshost.exe: Managed' has exited with code -2147023895 (0x800703e9).


If anyone can help me with this it would be great

It turns out I actually did have a stack overflow. I inherited the code and had several properties that look something like this:

int foo = 0; //lower case attribute name

int Foo // upper case property name
{
get{ return Foo; } // referencing the property, not the attribute
}

As it turns out, the property Foo was never referenced in code, so we never got an error during execution. However, when one runs through the debugger and inspects the object that Foo belongs to, the debugger executes the get on Foo, which then drops into an infinite loop of getting fun, and kills the debugger. We also get an error message that's a bit cryptic.

I'm guessing this is the problem being faced by the first post, since the stack trace looked pretty similar to what I was getting.

I just started running into this error. I don't believe it's a stack overflow error (unless it's a bug in the runtime itself), since the code I'm stepping through has gone through a loop all of one time and I can generate the problem.

I'm encountering this when I look at an object and try to expand some of its members. Primitive types are fine, but arrays won't expand to show the array elements. This is the only thing I've encountered, so far, that causes the crash. Expanding a complex object works just fine.

This is pretty frustrating. The problem only crops up in C# - expanding an array's elements in C++ works just fine.

Hi,

This is happening to me too, except in Visual Studio 2003 - BUT it's been happening ever since I installed Visual Studio 2005 side-by-side. I think the 2005 debugger overwrote the old debugger that 2003 used to use, because now I'm seeing the same symptoms as you: Debugged thread simply stops as soon as I pause in break-mode to examine some page variables & watch objects.

Have you found a solution? If so, please advise.

Thanks,

-Sabrina

Hi there,

No sure if your problem has been solved, but I found that my error was caused by IE's Advanced Option "Disable Script Debugging" having been unchecked.I believe theIDE unchecks it when you step through client code in VS 2005, but it sure did cause my debugger to freak out. Anyway, that's what solved my problem. I hope it works out for you as well.

-Sabrina

It turns out I actually did have a stack overflow. I inherited the code and had several properties that look something like this:

int foo = 0; //lower case attribute name

int Foo // upper case property name
{
get{ return Foo; } // referencing the property, not the attribute
}

As it turns out, the property Foo was never referenced in code, so we never got an error during execution. However, when one runs through the debugger and inspects the object that Foo belongs to, the debugger executes the get on Foo, which then drops into an infinite loop of getting fun, and kills the debugger. We also get an error message that's a bit cryptic.

I'm guessing this is the problem being faced by the first post, since the stack trace looked pretty similar to what I was getting.

I also had the exact same problem (with the exact same solution). So it is probably a stack overflow. Your post was much more helpful than the previous "answer"

Also my VS started suddenly to stop debugging when hitting certain breakpoints. The annoying thing is that there is no error message at all. It took me about 1 day until I got the idea to check the output window, where I saw the funny message code as described above. Thanks to the posts here I finally knew that I had to look for a recursion error. My one was slightly different than the ones above:

 

public override string ToString() {
  ...
  ToString();
}

It seems VsHost is calling the ToString() of the class being debugged, which in my case had a recursion bug.