The CLR started life long before it was adopted to run .NET code. Started as the Universal Runtime in Project 42, a highfaluting project that failed but whose parts survived in subsequent projects, like .NET. Continued into NGWS (Next Generation Windows Services) before it evolved as the execution engine for .NET. 42 was the building … Read more
This is what worked for me: Download the following DLLs: clr.dll mscordacwks.dll SOS.dll from this folder on the machine that generated the dump: C:\Windows\Microsoft.NET\Framework64\v4.0.30319 Run the following command. The path to SOS.DLL should be without quotes, unescaped path delimiters: .load path to downloaded SOS.DLL I think a new WinDbg session is required for this to … Read more
Jason Zander’s blog post explains it perfectly: The original name of the CLR team (chosen by team founder and former Microsoft Distinguished Engineer Mike Toutonghi) was “Lighting”. Larry Sullivan’s dev team created an ntsd extension dll to help facilitate the bootstrapping of v1.0. We called it strike.dll (get it? “Lightning Strike”? yeah, I know, ba’dump … Read more
The CLR runtime dll was renamed to clr.dll with .NET 4. So in order to load the correct version of SOS you need to adjust your .loadby command. I.e. .loadby sos clr Also, if you’re on 64 bit, you should install the 32 bit version of Debugging Tools for Windows as well in order to … Read more