Exception thrown by SOS

Question

I am just starting out with windbg / sos and I created a simple console testing application (which throws an unhandled exception). It seems that after loading sos I will get an exception on the next call.

For instance:

ntsd consoleapplication1.exe .symfix .reload g .loadby sos clr 

if i call:

 !threads "c0000005 Exception in C:\Windows\Microsoft.NET\Framework\v4.0.30319\sos.threads PC: 592b7713 VA: 00000000 R/W: 0 Parameter: 00000000" 

if i call:

 !ClrStack c0000005 Exception in C:\Windows\Microsoft.NET\Framework\v4.0.30319\sos.ClrStack PC: 592b7713 VA: 00000000 R/W: 0 Parameter: 00000000 

Each call after my first call will work (this is only the first call that does not work after loading SOS).

I tried this recommendation and recompiled my code with native code debugging turned on, but that didn't help.

Windbg Version: 6.3.9600.16384 X86

Answer 1

This seems to be a WinDbg problem. I tried this with the .NET 4.0 console application, x86 target. I did not check the "Enable custom code debugging" checkbox, as I did not do this before.

I can reproduce your problem in WinDbg (NTSD) 6. 3.9600 .16384 x86 with debug build and release.

For me, this works with WinDbg (NTSD) 6. 2.9200 .16384 x86 with debug build and release.

Since in any case, I often have the problem of duplicating output in 6.3, I still use version 6.2 as my default version of WinDbg.