ProcDump generates dumps containing valuable information about your application processes, among other elements, during an exception. ProcDump is commonly used by 4D developers to debug crashing or freezing 4D applications.

When using ProcDump in the command-line interface, specific selectors can be used depending on the type of exception: crash or hung.

ProcDump for crash:

"C:\Dumps\ProcDump\procdump64.exe" -accepteula "ApplicationName.exe" -w -ma -e C:\Dumps

ProcDump for hung:

"C:\Dumps\ProcDump\procdump64.exe" -accepteula "ApplicationName.exe" -w -ma -e -h "C:\Dumps"

The -h selector in the second command enables the generation of a dump when a hung type of exception occurs.

Here is a quick reminder of some essential selectors in ProcDump:

-w Wait for the specified process to launch if it's not running. -ma Write a 'Full' dump file.   - Includes all memory (Image, Mapped and Private).   - Includes all metadata (Process, Thread, Module, Handle, Address Space, etc.). -e Write a dump when the process encounters an unhandled exception. -h Write dump if process has a hung window (does not respond to window messages for at least 5 seconds).

Read more information about 4D and ProcDump.