I’m debugging using the Debugging Tools For Windows (WinDbg).  Debugging a native C++ process (no CLR loaded).

I find with every debugger command I run, I get annoying amounts of debugger logging spew saying “CLRDLL: No CLR image loaded (i.e. mscorwks.dll)”.

For example, when I dump a call stack I see:

0:000> kC

CLRDLL: No CLR image loaded (i.e. mscorwks.dll)

KERNELBASE!RaiseException

myapp!_CxxThrowException

..

CLRDLL: No CLR image loaded (i.e. mscorwks.dll)

CLRDLL: No CLR image loaded (i.e. mscorwks.dll)

CLRDLL: No CLR image loaded (i.e. mscorwks.dll)

CLRDLL: No CLR image loaded (i.e. mscorwks.dll)

CLRDLL: No CLR image loaded (i.e. mscorwks.dll)

CLRDLL: No CLR image loaded (i.e. mscorwks.dll)

CLRDLL: No CLR image loaded (i.e. mscorwks.dll)

CLRDLL: No CLR image loaded (i.e. mscorwks.dll)

WARNING: Stack unwind information not available. Following frames may be wrong.

Etc…

The fix to disable this spew is running:

.cordll –vd

The reason I saw this in my debugger is I have a startup script that runs:

.cordll -ve -u –l

This –ve means “enable vebose logging for CLR”.  Internally the debugger is trying to load CLR debugging support over and over and this is failing.  Running .cordll –vd disables the extended logging.

Note you can disable CLR integration with debugger to speed up the debugger command execution when debugging native code by running:

.cordll -d -u -vd

Read help on .cordll for details.