.cordll (Control CLR Debugging)
The .cordll command controls managed code debugging and the Microsoft .NET common language runtime (CLR).
.cordll [Options]
Parameters
Options One or more of the following options:
-l (lower-case L)
Loads the CLR debugging modules.
-I **** Module (upper-case i)
Specifies the name or base address of the CLR module to be debugged. For more information, see Remarks.
-u
Unloads the CLR debugging modules.
-e
Enables CLR debugging.
-d
Disables CLR debugging.
-D
Disables CLR debugging and unloads the CLR debugging modules.
-N
Reloads the CLR debugging modules.
-lp **** Path
Specifies the directory path of the CLR debugging modules.
-se
Enables using the short name of the CLR debugging module, mscordacwks.dll.
-sd
Disables using the short name of the CLR debugging module, mscordacwks.dll. Instead, the debugger uses the long name of the CLR debugging module, mscordacwks_<spec>.dll. Turning off short name usage enables you to avoid having your local CLR used if you are concerned about mismatches.
-ve
Turns on verbose mode for CLR module loading.
-vd
Turns off verbose mode for CLR module loading.
Environment
| Item | Description |
|---|---|
| Modes | User mode, kernel mode |
| Targets | Live, crash dump |
| Platforms | All |
Remarks
To debug a managed application, the debugger must load a data access component (DAC) that corresponds to the CLR that the application has loaded. However, in some cases, the application loads more than one CLR. In that case, you can use the I parameter to specify which DAC the debugger should load. Version 2 of the CLR is named Mscorwks.dll, and version 4 of the CLR is named Clr.dll. The following example shows how to specify that the debugger should load the DAC for version 2 (mscorwks).
.cordll -I mscorwks -lp c:\dacFolder
If you omit the I parameter, the debugger uses version 4 by default. For example, the following two commands are equivalent.
.cordll -lp c:\dacFolder
.cordll -I clr -lp c:\dacFolder
Sos.dll is a component that is used for debugging managed code. The current version of Debugging Tools for Windows does not include any version of sos.dll. For information about how to get sos.dll, see Getting the SOS Debugging Extension (sos.dll) in Debugging Managed Code Using the Windows Debugger.
The .cordll command is supported in kernel-mode debugging. However, this command might not work unless the necessary memory is paged in.