Dump Module Loading
When Visual Studio loads a crash dump (an old format dump created by the Dr. Watson utility before Windows XP), it loads the binary modules for the dump by matching the module name, linker timestamp, and file size. The module name is the base name, so exmpl will match either exmpl.exe or exmpl.dll.
When Visual Studio loads a minidump (a newer format created by Visual Studio and other newer tools), the name is the basename and the extension, so exmpl.dll will match exmpl.dll only.
Visual Studio assumes that modules are located in the same location as the dump and begins searching from that location. Suppose the following binary and modules were loaded when you created a dump:
D:\qa\exmpl\exmpl.exe D:\qa\exmpl\dll.dll F:\win2k\system32\ntdll.dlll F:\win2k\system32\kernel32.dll
The dump exmpl.dmp is found in this location:
Visual Studio searches the following locations:
C:\qa\dumps\exmpl.exe C:\qa\dumps\exmpl\exmpl.exe C:\qa\dumps\qa\exmpl\exmpl.exe D:\qa\exmpl\exmpl.exe C:\qa\dumps\dll.dll C:\qa\dumps\exmpl\dll.dll C:\qa\dumps\qa\exmpl\dll.dll D:\qa\exmpl\dll.dll C:\qa\dumps\kernel32.dll C:\qa\dumps\system32\kernel32.dll C:\qa\dumps\win2k\system32\kernel32.dll F:\win32\system32\kernel32.dll