Dump Module Loading
This topic applies to:
Edition |
Visual Basic |
C# |
C++ |
Web Developer |
|---|---|---|---|---|
Express |
.gif "Topic does not apply") |
|
.gif "Topic applies") |
|
Standard |
|
|
|
|
Pro and Team |
|
|
|
|
Table legend:
|
Applies |
|
Does not apply |
.gif "Topic applies but command hidden by default") |
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:
C:\qa\dumps\exmpl.dmp
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.