title: How to benefit from heap tagging by DLL?
body: <p>How do I use and benefit from the GFlags setting <a href="http://msdn.microsoft.com/en-us/library/windows/hardware/ff542915%28v=vs.85%29.aspx" rel="noreferrer">Enable heap tagging by DLL</a>?</p>
  
  <p>I know how to activate the setting for a process, but I did not find useful information in the output of <code>!heap -t</code> in WinDbg. I was expecting some output like this:</p>
  
  <pre><code>0:000&gt; !heap -t
  Index   Address   Allocated by 
  1:      005c0000  MyDll.dll
  2:      006b0000  AnotherDll.dll
  </code></pre>
  
  <p>so that I can identify which heap was created by which DLL and then e.g. identify the source of a memory leak.</p>
  
  <p>Is this a misunderstanding of the term "heap tagging by DLL" or do I need some more commands to get to the desired result?</p>
  
  <p>My research so far:</p>
  
  <ul>
  <li>I googled for a tutorial on this topic, but I couldn't find a detailed description</li>
  <li>I read WinDbg's <code>.hh !heap</code> but it's not explained there in detail as well. Tag is only used in <code>!heap -b</code></li>
  </ul>