<<< There are also some very important information in FAQ.

1. Preparation

One of the MOST IMPORTANT things to check memory leak with RuntimeChecker is create PDB files.

Next diagram shows how to create PDB file for debug version and release version.

1.1 Debug

1.2 Release

Config PDB file for release version in Visual Studio 6, part 1

Config PDB file for release version in Visual Studio 6, part 2

2. Copy PDB fles

Copy PDB files to the directories of their corresponding EXE,DLL or OCX files. 

Make sure copy the latest PDB files the directories, especially after changing code. 

This step is very important!!! 

Usually you need to check whether PDB files are consistant whenever you find call stack 

information looks strange or wrong.

3. Choose the target application

Customer can either use RuntimeChecker to create a process or attach to a running process 

Start a new process

Attach to a running process

4. Setting

4.1 General

General setting is to configure working path, command line and source code path.

General Setting  

4.2 Modules

Modules setting is to choose which modules will be monitored. 

Modules Setting

4.3 configure call stack depth

CallStack Setting

5. Run

Run the application by clicking the "Run" button on setting window.

6. Checking result

Shut down the target application GRACEFULLY.(You should not kill your application from task manager)

All of the memory leak will be showed on memory usage tab. The upper window shows the allocated memory

and the call stacks. The other windows shows the source code if you double click the call stack with line

 number.

 

If neither manual nor FAQ answered your questions, please feel free to send email to support@runtimechecker.com

<<< There are also some very important information in FAQ.