.NET Failover Using SOS.dll

Question

I am working on a mixed application (C ++ / CLI, C ++, some C #), and when it falls into the field, a memory dump is created. I usually get these dumps from the client and try to figure out what went wrong.

The question is how to deal with post-mortem debugging of managed code? I usually use WinDbg with SOS.dll, but it seems that SOS does not support backward compatibility! I recently launched Windows Update, and now I can’t download thumbnails from the client’s site. He complains about the wrong version of SOS.

How can I download and download previous version (s)? Am I doing something wrong?

Answer 1

This is probably an x86 / 64 issue. How do you download sos?

You can try loading sos using:

.loadby sos mscorwks 

Or, if it is not, try loading the 64-bit sos explicitly:

 .load c:\Windows\Microsoft.NET\Framework64\v4.0.30319\SOS.dll 

Answer 2

I had the same problem. Look at the WinDbg stack overflow question : copy of SOS.dll x86 4.0.30319.237 , it offers an alternative to downloading and linking to the correct version of SOS from the server.