Tag Archives: debugging

How to collect process dump with LeakTrack information using ProcDump + Debug Diagnostic Tool

Just a short note on how to collect process dump including LeakTrack information.

Download latest version of Microsoft Debug Diagnostic Tool, at the moment it is Debug Diagnostic Tool v2 Update 3 and install it going through an installation wizard steps as shown below:

Debug Diagnostics Installation Wizard Page 1
Debug Diagnostics Installation Wizard Page 2
Debug Diagnostics Installation Wizard Page 3
Debug Diagnostics Installation Wizard Page 4
Debug Diagnostics Installation Wizard Page 5

Once installation wizard completes, download ProcDump and unzip it on the server where you going to collect dump file. Next, run DebugDiag 2 Collection:

DebugDiag 2 Collection icon in Start Menu

Cancel out initial “Select Rule Type” dialog:

Debug Diagnostic Tool – Select Rule Type

Navigate to Processes tab select process for which you need to collect
LeakTrack, right click on it and select Monitor For Leaks:

Debug Diagnostic Tool – Monitor For Leaks

Click Yes in “Do you want to enable ‘Service Mode’ and continue” pop up:

Debug Diagnostic Tool – Enable Service Mode

You will see confirmation that monitoring for leak has started:

Debug Diagnostic Tool – Monitoring for leaks in the specified process

Now let it run and wait till the process you monitor use up large amount of RAM and take dump using procdump.exe, you can see some hints on the command line syntax below:

Script to run procdump.exe

Once dump taken you can stop monitoring for leaks and close Debug Diagnostic tool:

Debug Diagnostic Tool – Stop Monitoring For Leaks

After following steps above your process memory dump should contain LeakTrack information. You can tell that by the dump file size – if you take a dump without enabling Monitor For Leaks option in Debug Diagnostic Tool at the same time you will see that your dump file size will be smaller if compared with one which you take while running Monitor For Leaks .

Please follow and like us:

How to take process dump using CDB

Just a short explanation of how to take process dump using CDB.

First you need to get Debugging Tools for Windows. To get Debugging Tools as a standalone tool set you can just download Windows SDK and during installation select Debugging Tools for Windows:

Installing Debugging Tools for Windows

Once Debugging tools for Windows are downloaded and installed you can find cdb.exe in the following location – C:\Program Files (x86)\Windows Kits\10\Debuggers\x64 (note that number highlighted in bold may vary depending on SDK version installed – in my case it is 10, and you obviously have cdb.exe for different platforms – x86/x64 etc. – just navigate to appropriate subfolder of Debuggers folder).

To take dump launch CMD in elevated mode, switch directory to CDB location and execute cdb -p <PROCESS PID> to take crash dump (remember that PID information can be found in Task Manager or retrieved with PowerShell using Get-Process “%ProcessName%” | select -expand id):

CDB attaching to the process by PID

At this stage CDB is attached to process and closing this CMD window will terminate process you are attached to. Once CDB is loaded type in the following commands:

..loadby sos clr


You will receive “No export Thread found” error – it can be ignored, and some more commands needs to be executed. First run !StopOnException -create System.StackOverflowException it may not work from the first attempt, just re-run it once again until you see confirmation that breakpoint was created:

CDB set breakpoint

Once breakpoint is set type gn and wait for process crash:

When process crashed the following commands have to be executed:

.logopen C:\dumps\k2hostserver.log



.dump /ma /u C:\dumps\process.dmp




Repeat typing gn until you get “there is no debugee” message. Your dump will be written in the location you specified above (C:\dumps\process.dmp).

Please follow and like us: