|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
Dump Module Loading
This topic applies to:
Pro and Team
Does not apply
Command or commands hidden by default.
When you load a dump in Visual Studio, the debugger looks for modules beginning in the same location as the dump. 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
In previous versions of Visual Studio, the MODPATH argument was used to specify additional module search paths. Visual Studio 2005 looks for modules in the specified symbol search paths and does not use MODPATH.