How do I specify the debugger extension of a command?

The problem is that you are reading the dump file and running a command, but you think the output of this command is a little different from that you usually see. you are confused, wondering if this command does not belong to the desired debugger extension. what should I do?

 

For example, psscor2.dll and sos. dll both contain some commands. Your debugger loads two debugger at the same time, and you run one! Threads, but it is unclear whether the command is psscor2.dll or sos. dll.

 

Solution

==============

First, specify debugger extension. Use the following format

! [DebuggerExtension]. [Command] Arguments

 

Example:

! Psscor2.threads-special

 

Second, run the. chain command to check the order of the loaded debugger extension. The command of the loaded debugger will be found first.

0: 018>. chain
Extension DLL search Path:
C: \ Program Files \ Debugging Tools for Windows (x64) \ WINXP; C: \ Program Files \ Debugging Tools for Windows (x64) \ winext; C: \ Program Files \ Debugging Tools for Windows (x64) \ winext \ arcade; C: \ Program Files \ Debugging Tools for Windows (x64) \ pri; C: \ Program Files \ Debugging Tools for Windows (x64); C: \ Program Files \ Debugging Tools for Windows (x64) \ winext \ arcade; C: \ Windows \ system32; C: \ Windows; C: \ Windows \ System32 \ Wbem; C: \ Windows \ System32 \ WindowsPowerShell \ v1.0 \

Extension DLL chain:
C: \ Windows \ Microsoft. NET \ Framework64 \ v2.0.50727 \Sos: Image 2.0.50727.4952, API 1.0.0, built Thu May 13 20:15:18 2010
[Path: C: \ Windows \ Microsoft. NET \ Framework64 \ v2.0.50727 \Sos. dll]
Psscor2: Image 2.0.0.1, API 1.0.0, built Thu Mar 25 03:25:01 2010
[Path: C: \ Program Files \ Debugging Tools for Windows (x64 )\Psscor2.dll]
Dbghelp: image 6.11.0001.404, API 6.1.6, built Thu Feb 26 10:10:27 2009
[Path: C: \ Program Files \ Debugging Tools for Windows (x64) \ dbghelp. dll]
Ext: image 6.11.0001.404, API 1.0.0, built Thu Feb 26 10:10:26 2009
[Path: C: \ Program Files \ Debugging Tools for Windows (x64) \ winext \ ext. dll]
Exts: image 6.11.0001.404, API 1.0.0, built Thu Feb 26 10:10:17 2009
[Path: C: \ Program Files \ Debugging Tools for Windows (x64) \ WINXP \ exts. dll]
Uext: image 6.11.0001.404, API 1.0.0, built Thu Feb 26 10:10:20 2009
[Path: C: \ Program Files \ Debugging Tools for Windows (x64) \ winext \ uext. dll]
Ntsdexts: image 6.1.7015.0, API 1.0.0, built Thu Feb 26 10:09:22 2009
[Path: C: \ Program Files \ Debugging Tools for Windows (x64) \ WINXP \ ntsdexts. dll]

From the above command, we can see that here SOS. the command in dll is first searched. because. the chain command will list the loaded debugger extension according to the default search order. so in this case, run! The threads command is executed in SOS. dll.

 

The. chain Command help information is as follows:

. Chain (List Debugger Extensions)

The. ChainCommand lists all loaded debugger extensions in their default search order.