I've gotten a Dr. Watson crash dump file from an end user of my app.
I've loaded it in Visual Studio 7 and "Ran" it. The modules window
says "No matching binary found" for my app. I do have the app in that
same path on my machine - it is the same version as what the user was
running. Why do I get "No matching binary found"? What does Visual
Studio look for when trying to match my local file with the crashed
one?

More Details:
The crash is reported in ver 4.24.1.0 of my app. When that version was
built, it, and its associated .pdb file, they were archived in Visual
SourceSafe for just such a moment. I pulled this archived version from
VSS and dropped it in the correct path but VS still tells me 'no match
found'. I noticed that the Timestamp noted in the modules window in VS
was different that the file pulled from VSS (when pulled from VSS, the
Date Modified date of the file matched when it was pulled from VSS). I
tried changing the date using a utility but that did not help.

I've gone thru this exercise before and things worked but that
exercise did not include the Visual SourceSafe part.

I've searched the internet and found almost nothing to help me
understand what criteria VS uses for matching the dump file to a local
file.

Any help is greatly appreciated.

Randy

[quoted text, click to view]

It is a minidump.

[quoted text, click to view]

What kind of crash dump is it? Minidump or old-style full dump?
For minidumps, module matching rules are described here:
http://www.debuginfo.com/articles/matchmodules.html

If it is an old-style full dump (created on Windows 2000 or older system),
use WinDbg to debug it - WinDbg should be able to get all the necessary information
from the dump itself (without the need to find matching modules).

Regards,
Oleg
[VC++ MVP]