Dump files of. net framework 2 are usually used. A. net 1.1 dump file has many problems.
After some exploration, I finally successfully checked the dump.
The solution is as follows:
1. Install. net framework 1.1 on the machine where the debugger is located.
2. Install. net fraemwork 1.1 SP1 on the machine where the debugger is located
3. When using. loadby sos mscorwks, an error is reported, as follows:
"Unable to find module 'mscorwk '"
4. Use the following command to load sos
. Load C: \ Windows \ Microsoft. NET \ Framework \ v1.1.4322 \ sos. dll
5. succeeded. Run! Clrstack ,! Dumpstackobjects is okay.
Note that psscor2 cannot be used to view dump files of. net framework 1.1. Only sos. dll files that come with. net 1.1 can be used.
When psscor2 is loaded, use it! The clrstack command will encounter the following errors:
Doesn't work with 1.xFailed to load data access DLL, 0x80004005Verify that 1) you have a recent build of the debugger (6.2.14 or newer) 2) the file mscordacwks.dll that matches your version of mscorwks.dll is in the version directory 3) or, if you are debugging a dump file, verify that the file mscordacwks___.dll is on your symbol path. 4) you are debugging on the same architecture as the dump file. For example, an IA64 dump file must be debugged on an IA64 machine.You can also run the debugger command .cordll to control the debugger'sload of mscordacwks.dll. .cordll -ve -u -l will do a verbose reload.If that succeeds, the SOS command should work on retry.If you are debugging a minidump, you need to make sure that your executablepath is pointing to mscorwks.dll as well.
References:
Back to Basics-How do I get the memory dumps in the first place? And what is SOS. dll?
Http://blogs.msdn.com/ B /tess/archive/2006/01/11/511773.aspx
"Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg
Http://blogs.msdn.com/ B /tess/archive/2008/05/13/failed-to-start-stack-walk-80004005-following-frames-may-be-wrong-and-other-errors-you-may-see-in-windbg.aspx