To open the Modules window, you must be debugging. From the Debug menu, choose Windows and click Modules.
Note This feature is not available for script or SQL debugging.
The Modules window lists the modules, which are DLL or EXE files, used by your program. It shows the following information for each module:
- Module name, which has a .dll or .exe file name extension.
- Memory locations occupied by the module.
- Path name of the DLL or EXE on your hard disk.
- Load order. The first module loaded is number 1.
- Version number of the module.
- Program ID number and program type.
- The time the module was created.
- Whether debug information for the module has been loaded.
By default, the Modules window sorts modules by load order. However, you can sort by any column by choosing the button at the top of the column.
If a module appears with a red exclamation point and an asterisk next to the address, the module was loaded at a relocated base address, due to the fact that another module was already loaded at that address. Therefore, your application suffers the performance hit of having a module relocated. You may want to change the base address. For more information, see /BASE (Base Address).
If the symbols (.pdb) file for a particular module is not loaded (especially when doing remote debugging), you can manually load the symbols by right-clicking on the module and then selecting Reload Symbols. Since the debugger attempted and failed to load symbols for all modules at startup time, browse to the appropriate folder and select the .pdb file. If you highlight more than one module and right-click, you will be prompted to select a folder. The debugger will try to match symbol files (in the folder) for all selected modules.