Export (0) Print
Expand All

Specifying Additional Dump Module Search Paths

Visual Studio .NET 2003

You can specify additional module search paths for a specific dump.

To specify additional module paths in Visual Studio

  • Specify them in the Command Arguments grid of the Property Pages dialog box. The syntax looks like this:
    MODPATH =c:\temp\xyz;d:\temp;f:\abc\temp
    

When you load a dump, MODPATH and EXTS arguments specified in Command Arguments affect the loading of the dump. Other command arguments, which are intended for a debugged program rather than a dump, are ignored.

The MODPATH example tells Visual Studio to look for ntdll.dll in these directories:

C:\temp\xyz\ntdll.dll
D:\temp\ntdll.dll
F:\abc\temp\ntdll.dll  
C:\qa\dumps\ntdll.dll
C:\qa\dumps\system32\ntdll.dll
C:\qa\dumps\win2k\system32\ntdll.dll
F:\win32\system32\kernel32.dll

Alternately, you can specify a global module search path in the Registry, using the following registry keys:

  • HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\7.1\NativeDE\Dumps\GlobalModPath
  • HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\7.1\NativeDE\Dumps\GlobalModPath

Each key is a string value (REG_SZ), which can be set to a global search path. The debugger interprets these paths as if they had been specified with the MODPATH argument. The debugger searches the HKEY_CURRENT_USER... path before the HKEY_LOCAL_MACHINE... path.

See Also

Dump Module Loading | Dumps

Show:
© 2014 Microsoft