Export (0) Print
Expand All

Dump Module Loading

This topic applies to:

Edition

Visual Basic

C#

F#

C++

Web Developer

Express

Topic does not applyTopic does not applyTopic does not applyTopic does not applyTopic does not apply

Pro, Premium, and Ultimate

Topic applies

Topic applies

Topic does not apply

Topic applies

Topic applies

When you load a dump file in Visual Studio 2010, the debugger looks for modules starting in the same location as the dump file. Suppose the following binary and modules were loaded when you created a dump file:

D:\qa\exmpl\exmpl.exe
D:\qa\exmpl\dll.dll
F:\win2k\system32\ntdll.dlll
F:\win2k\system32\kernel32.dll

The dump file exmpl.dmp is found in this location:

C:\qa\dumps\exmpl.dmp

Visual Studio 2010 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 earlier versions of Visual Studio, the MODPATH argument was used to specify additional module search paths. Visual Studio 2010 looks for modules in the specified symbol search paths and does not use MODPATH.

Community Additions

ADD
Show:
© 2014 Microsoft