Address: http://blogs.msdn.com/ B /dougste/archive/2011/10/31/tips-for-successful-net-debugging-with-windbg.aspx
1. The windbg version is the same. During analysis and dump, The windbg version is the same, and it must be a complete memory file. Run with. Dump/Ma c: \ dump. dmp
2. Check that the CLR versions are consistent. Check whether mscorwks. dll (#2.0) or CLR. dll (#4.0) is correct. Use lm VM mscorwks or Lm vm clr check to check whether the output content contains # m c or the like. If yes, the file does not match.
3. loaded the correct extension command. Check whether the loaded extension is psscor2.dll (#2.0) psscor4.dll (#4.0 ). Use the command! Threads checks whether the extension works properly. Psscor2: http://www.microsoft.com/download/en/details.aspx? Id = 1073
Psscor4: http://www.microsoft.com/download/en/details.aspx? Id = 21255
4. If Step 3 fails, check whether the same DAC (Data Access Component) as the CLR version is correct. Run mscordacwks.dllw.beibeibeito the same directory of windbg.exe and name it mscordacwks_xpp_xpp_2.0.50727.vvvv.dll on the dump machine. For more information, see "failed ".
To load data access DLL, 0x80004005 "-or-what is mscordacwks. dll? "
5. Check the CLR version. Use lm VM mscorwks (#2.0) or Lm vm clr (#4.0) to confirm the CLR version. CLR 2.0 version history: http://blogs.msdn.com/ B /dougste/archive/2007/09/06/version-history-of-the-clr-2-0.aspx CLR 4.0 version history: http://blogs.msdn.com/ B /dougste/archive/2011/09/30/version-history-of-the-clr-4-0.aspx
6. A very powerful extension command for debugging and hosting code. Sosex: Step 6 of benchmark is the prerequisite for "ensuring successful debugging of. Net in windb". Each step is very important. Remember, remember! 2. Regarding the CLR version list, foreign Daniel is a good summary for convenient search and should be a useful tool for. Net debugging. 3. In addition to SOS. DLL for hosting and debugging, there are two Swiss Army knives available: psscor2/sosex
