title: DebugDiag call stack does not display line number of functions in call stack
body: <p>I am trying to isolate memory leaks in native code on Windows.</p>
  
  <p>I ran multiple iterations of a test case and attached DebugDiag to the process to collect information on the suspected leak (memory leak confirmed through multiple runs in PerfMon).</p>
  
  <p>DebugDiag pointed out suspicious call stacks like </p>
  
  <pre><code> Call stack sample 1
  
   Address   0x0f09e2c0
  
   Allocation Time   00:22:38 since tracking started 
  
   Allocation Size   8.54 KBytes 
  
      Function                                       Source destination
      ntdll!RtlpReAllocateHeap+19c                  ntdll!RtlAllocateHeap 
      ntdll!_except_handler4       
      ntdll!RtlReAllocateHeap+22f                   ntdll!RtlReAllocateHeap 
      sqlncli11!MpReallocZeroMemory+66     
      sqlncli11!SQLReAllocateMemoryEx+22            sqlncli11!MpReallocZeroMemory 
      sqlncli11!AllocPlex+1a4                       sqlncli11!SQLReAllocateMemoryEx 
      sqlncli11!SetADRec+2a4                        sqlncli11!AllocPlex 
      sqlncli11!SQLBindCol+217                      sqlncli11!SetADRec 
      odbc32!SQLBindCol+3c0       
      sscfdm!CSSLockSqlCursor::DoExecuteStmt+11a       
      sscfdm!CSSSqlCursor::Execute+129              sscfdm!CSSLockSqlCursor::DoExecuteStmt 
      sscfdm!CSSSqlObj::Execute+d86                 sscfdm!CSSSqlCursor::Execute 
      sscfom!CSSBusComp::SqlExecute+3a              sscfdm!CSSSqlObj::Execute 
      &lt;&lt;many multiple lines below&gt;&gt;
  </code></pre>
  
  <p>I have configured symbols properly, now I wanted to know how do I extract more info from call stack. </p>
  
  <ol>
  <li><p>UMDH logs have line numbers too (with file names) in their diff logs. However in DebugDiag report I do not find any line numbers of those functions. If the functions are really very long, then it becomes difficult to describe the context by just looking at call stack without having the line numbers. Is there any way I can extract line number of function (file) from DebugDiag logs?</p></li>
  <li><p>Another thing I wanted to know was the significance of hex offset with each <code>module!function</code> entry in the call stacks.</p></li>
  <li><p>What is the Allocation size in the call stack? is it the allocated memory that has not been freed (hence the leak) per execution of this call stack?</p></li>
  <li><p>Any pointers to comprehensive documentation about DebugDiag capabilities?</p></li>
  </ol>