Verifying DLLs Loaded into Memory
When troubleshooting a problem or debugging an application, it's often helpful to verify which DLLs are loaded in your PC memory. Each DLLs loaded in memory are associated with a running process or application. The following utilities are third party products that can be used to list all DLLs to aid in troubleshooting (these utilities run on 32 bit Winter platforms only):· Msinfo32Note: 'ListDLLs' and 'Handle' are handy command line utilities which have their GUI analog in the 'Process Explorer'.
· Process Explorer
· List DLLs
· Handle
How to obtain and use the third party products:
Msinfo32.exe is an utility that can be installed with Microsoft Office. Default directory is Program Files\Common Files\Microsoft Shared\MSInfo directory. The Microsoft System Information (MSINFO) is a basic tool for gathering system configuration. It is intended primarily to help Windows users determine information that could indicate problems with their systems. For example, to find out the module name, version number, file date, file size, bit (16 or 32) and fully qualified path to all modules in memory.To use:
1. Open a Windows application in development mode or run an executable
file.
2. Run Msinfo32.exe from Microsoft Explorer or the Run command from
the Start menu.
3. Microsoft System Information" window displays two panes. The left
pane displays system information options and the right pane display detail
information of selected option on the left pane.
4. To see DLLs are loaded into a memory, select Software Environment
then Loaded Modules category from the bottom of the left pane. Each item
from the Loaded Modules category represents an application extension or
a system resource that is currently loaded in memory. The right pane lists
the DLL name, fully qualified path to all modules (drivers, fonts, dynamic
link libraries and executable files), process, DLL version, size, date
and manufacturer in memory.
5. To print the output, select Print option from the File menu. To
save the output into a file, select Save from the File menu.
6. To sort any menu item, click on a column title. For example, by
clicking on the Path column title, DLLs are shorted within the directories.
Process Explorer is a GUI/device driver
combination that together shows information about which handles and DLL
processes have opened and loaded in memory. The unique capabilities of
Process Explorer make it useful for tracking down DLL version problems
or handle leaks, and provide insight into the way Windows and applications
work and more. This free-ware is written by Mark Russinovich and it can
be downloaded from the web site URL:
http://www.sysinternals.com/ntw2k/freeware/procexp.shtml
Note: HandleEx has been renamed to Process Explorer
To use:
1. Download Process Explorer zip file from the from the above web url
to your local driver and unzip it. Process Explorer must locate on your
non-network drive that you must have administrative privilege to run it.
2. Open a Windows application from development or run an executable
file.
3. Run Process Explorer from Microsoft Explorer or from the Run command
from the Start menu. When Process Explorer is started for the first time
it will be in handle-mode. Menus, hot-keys, or toolbar buttons can be used
to refresh the display or switch to DLL-mode. See more details at the web
site or on-line help. Process Explorer display consists of two sub-windows.
The top window always shows a list of the currently active processes. The
bottom window shows list of DLLs loaded for select active process and having
details like the name, version, date and fully qualified path to every
DLL loaded into memory.
4. From the Process tab of the top window, search and select an executable
file by scrolling the horizontal scroll bar.
5. Select the "View DLLs" menu item from the View menu or the equivalent
toolbar button to switch to "View Handles" mode. In this mode loaded DLL
are listed in the bottom window.
6. To sort any menu item, click on a column title. For example, by
clicking on the Path column title, DLLs are shorted within the directories.
7. To save the output: Select an option File ->Save As.
ListDlls.exe This utility will show which DLLs are loaded on Windows for all running processes/applications. It shows you the fully qualified path names of loaded modules with names. ListDLLs supported on Windows 9x, NT 3.51, NT 4.0, and Win2K. This free-ware is also written by Mark Russinovich and it can be downloaded from the Web site http://www.sysinternals.com/ntw2k/freeware/listdlls.shtml
To use:
1. Download and copy the ListDLLs into your machine executable path
2. Open a Windows application from development or run an executable
file.
2. Go to DOS command prompt:
Type ?listdlls > outputfile.txt? where listdlls
? name of utility and send the output to outputfile.txt ? name of output
file that has all dlls information
OR
Start menu - run and type ?listdlls > outputfile.txt?,
if ListDLLs utility is included in your system PATH
Handle.exe utility that displays information about open handles for any process in the system. You can use it to see the programs that have a file open, or to see the object types and names of all the handles of a program. This free-ware is also written by Mark Russinovich and it can be downloaded from the Web site http://www.sysinternals.com/ntw2k/freeware/handle.shtml
To use:
1. Download and copy the Handle into your machine executable path
2. Open a Windows application from development or run an executable
file.
2. Go to DOS command prompt:
Type ?Handle > outputfile.txt? where Handle
? name of utility and send the output to outputfile.txt ? name of output
file that have all open handles for any processes information
OR
Start menu - run and type ?Handle > outputfile.txt?,
if ?Handle utility is included in your system PATH
Disclaimer: These products are produced by third parties and the information provided by this document is intended to provide guidance and information to Sybase customers. Sybase Inc. does not guarantee the accuracy or current status of these products.
Back to Top
