User Mode Dump Files Must be Debugged on Same Architecture

• Microsoft Windows NT, versions 3.1, 4.0
• Microsoft Windows NT Advanced Server
• Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
• Microsoft Windows NT Server versions 3.5, 3.51, 4.0

SUMMARY

User-mode dump files must be debugged using Windbg on the same type of architecture they were created on.

MORE INFORMATION

Windbg.exe can be configured to remotely debug a different architecture by modifying the Expression Evaluator, Transport Layer, and Execution Model by selecting Debugger.dll from the Options menu. However, debugging user-mode dump files must be done on the same type of architecture they were created on.

Windbg.exe uses the Transport Layer setting to determine the CPU type. If the Transport Layer is configured for Local, then it determines the CPU type of the local computer. If the Transport Layer is configured for either of the serial options or pipes, then it determines the CPU type for the remote computer. In either case, Windbg.exe compares the CPU type returned through the Transport Layer to the specified architecture versions of the Expression Evaluator and Execution Model. WINDBG fails to load the user- mode dump file if these do not match.

For example, the following messages will appear when you attempt to debug an Alpha user-mode dump file created on an X86 computer:

Wrong EE specified, overridden by eecxxx86.dll
Wrong EM specified, overridden by emx86.dll

The file c:\user.dmp cannot be opened.

Additional query words: watson nt32ap debugref

Keywords : kbnetwork ntstop NTSrvWkst
Version : winnt:3.1,3.5,3.51,4.0; :
Platform : winnt
Issue type : kbinfo