In this article we will tell you everything you need to know about ProcDump. From its origin and evolution over the years to its relevance today, through its different applications and uses. ProcDump has been a topic of interest to many people, and in this article we will try to address every relevant aspect related to ProcDump. It doesn't matter if you are an expert in the field or if you are just starting to delve into this topic, here you will find valuable information that will help you better understand ProcDump and its importance in different areas.
| ProcDump | |
|---|---|
ProcDump v9.0 | |
| Original author | Winternals Software |
| Developer | Microsoft |
| Stable release | v11.0 (Windows version) v1.3 (Linux version)[1] / November 3, 2022 (Windows version) November 3, 2022 (Linux version) |
| Repository | github |
| Written in | C |
| Operating system | Microsoft Windows, Linux |
| Available in | English |
| License | Windows: Proprietary commercial software Linux: MIT License |
| Website | docs |
ProcDump is a command-line application used for monitoring an application for CPU spikes and creating crash dumps during a spike.[2][3] The crash dumps can then be used by an administrator or software developer to determine the cause of the spike. ProcDump supports monitoring of hung windows and unhandled exceptions. It can also create dumps based on the values of system performance counters.[4]
Initially, ProcDump was only available for Microsoft Windows. In November 2018, Microsoft confirmed it is porting Sysinternals tools, including ProcDump and ProcMon, to Linux.[5] The software is open source. It is licensed under MIT License and the source code is available on GitHub.[6]
The Linux version requires Linux kernels version 3.5+ and runs on Red Hat Enterprise Linux / CentOS 7, Fedora 26, Mageia 6, Ubuntu 14.04 LTS. It currently does not have full feature parity with the Windows version (e.g. custom performance counters).
Create five core dumps ten seconds apart of the target process with process identifier (pid) == 1234
$ sudo procdump -n 5 -p 1234