title: Invalid call stack in crash dump due to mismatched/missing *system* binary file?
body: <p>Got this callstack when I open a Windows crash dump in Visual Studio 2005:</p>
  
  <pre><code>&gt;   myprog.exe!app_crash::CommonUnhandledExceptionFilter(_EXCEPTION_POINTERS * pExceptionInfo=0x0ef4f318)  Line 41  C++
      pdm.dll!513fb8e2()  
      [Frames below may be incorrect and/or missing, no symbols loaded for pdm.dll]   
      kernel32.dll!_UnhandledExceptionFilter@4()  + 0x1c7 bytes   
      ...
  </code></pre>
  
  <p>Looking at the module load info:</p>
  
  <pre><code>...
  'DumpFM-V235_76_1_0-20110412-153403-3612-484.dmp': Loaded '*C:\Program Files\Common Files\Microsoft Shared\VS7Debug\pdm.dll', No matching binary found.
  ...
  </code></pre>
  
  <p>We see that this binary was not even loaded, because the machine used to analyze the dump is a different machine than the machine that produced the dump.</p>
  
  <p>I don't have access to this other machine at the moment -- can I somehow get this stack fixed, or will I always need the exact binary at this exact path location?</p>