title: How to extend the set of APIs visible to the logexts extension of windbg/cdb/ntdb?
body: <p>I trace certutil using the following cdb script (named TraceScript.txt):</p>
  
  <pre><code>!logexts.loge c:\logs
  !logexts.logc e *
  !logexts.logo d d
  !logexts.logo d t
  !logexts.logo e v
  g
  !logexts.logb f
  q
  </code></pre>
  
  <p>and the following batch file (named trace.cmd):</p>
  
  <pre><code>@echo off
  set SYMBOL_PATH=srv*c:\users\markk\appdata\local\temp\symbolcache
  cdb -y %SYMBOL_PATH% -cf c:\utils\TraceScript.txt %*
  </code></pre>
  
  <p>All is fine, but I have noticed the following line in the output:</p>
  
  <pre><code>[LogHookComInterface] Interface {7a18edde-7e78-4163-8ded-78e2c9cee924} is unknown -- not logging.
  </code></pre>
  
  <p>Where the GUID corresponds to the following registry path:</p>
  
  <pre><code>HKEY_CLASSES_ROOT\Interface\{7A18EDDE-7E78-4163-8DED-78E2C9CEE924}
  </code></pre>
  
  <p>Which in turn corresponds to the <code>ICertConfig2</code> interface - seems relevant, isn't it?</p>
  
  <p>Anyway, I am wondering whether it is possible to make this interface visible to the logger, because without it all the logging is useless. How do I know it? The logger reports a single invocation of the CoCreateInstance API with the GUID 372FCE38-4324-11D0-8810-00A0C903B83C, which corresponds to the CertConfig class, which I guess implements the ICertConfig2 interface. No other certificate related APIs appear in the log. So without the ICertConfig2 interface the log is useless.</p>
  
  <p>Any ideas?</p>
  
  <p><em>P.S.</em></p>
  
  <p>I will gladly accept ways to trace the ICertConfig2 COM API.</p>