man(8)

πŸŽ€ NAME πŸŽ€

okay bestie, listen up β€” this is procdump, and you're reading it in the man(8) manual section πŸ’–. What does it do? It generates coredumps based off performance triggers. Yes, for real. Your app does a weird little performance thing and boom πŸ’₯ you get a core dump. iconic behavior, honestly.


✨ SYNOPSIS ✨

Here's the whole shape of it, no cap β€” type it exactly like this:

procdump [-n Count]
         [-s Seconds]
         [-c|-cl CPU_Usage]
         [-m|-ml Commit_Usage1[,Commit_Usage2...]]
         [-gcm [<GCGeneration>: | LOH: |
POH:]Memory_Usage1[,Memory_Usage2...]]
         [-gcgen Generation]
         [-restrack [nodump]]
         [-sr Sample_Rate]
         [-tc Thread_Threshold]
         [-fc FileDescriptor_Threshold]
         [-sig Signal_Number1[,Signal_Number2...]]
         [-pc|-pcl Provider:Counter[pN] Threshold]
         [-e]
         [-f Include_Filter,...]
         [-fx Exclude_Filter]
         [-mc Custom_Dump_Mask]
         [-pf Polling_Frequency]
         [-o]
         [-log syslog|stdout]
         {
           {{[-w] Process_Name | [-pgid] PID} [Dump_File | Dump_Folder]}
         }

πŸ¦‹ Options:

every single flag, in order, nothing skipped, because we respect the source πŸ’…

  • -n β€” Number of dumps to write before exiting.
  • -s β€” Consecutive seconds before dump is written (default is 10).
  • -c β€” CPU threshold above which to create a dump of the process.
  • -cl β€” CPU threshold below which to create a dump of the process.
  • -m β€” Memory commit threshold(s) (MB) above which to create dumps.
  • -ml β€” Memory commit threshold(s) (MB) below which to create dumps.
  • -gcm β€” [.NET] GC memory threshold(s) (MB) above which to create dumps for the specified generation or heap (default is total .NET memory usage).
  • -gcgen β€” [.NET] Create dump when the garbage collection of the specified generation starts and finishes.
  • -restrack β€” Enable memory leak tracking (malloc family of APIs). If used without other triggers, use 't' to manually capture a restrack report. When used with other triggers, the 'nodump' option can be used to prevent dump generation and only produce restrack report(s).
  • -sr β€” Sample rate when using -restrack.
  • -tc β€” Thread count threshold above which to create a dump of the process.
  • -fc β€” File descriptor count threshold above which to create a dump of the process.
  • -sig β€” Comma separated list of signal number(s) during which any signal results in a dump of the process.
  • -pc β€” [.NET] Trigger when performance counter is at or exceeds the threshold. Format: provider_name:counter_name[pN] threshold. Supports both EventCounters and System.Diagnostics.Metrics. For histogram instruments, append [pN] to select a percentile (e.g., [p50], [p95], [p99]). Default is p50 if omitted.
  • -pcl β€” [.NET] Trigger when performance counter falls below the threshold. Format: provider_name:counter_name[pN] threshold.
  • -e β€” [.NET] Create dump when the process encounters an exception.
  • -f β€” Filter (include) on the content of .NET exceptions (comma separated). Wildcards (*) are supported.
  • -fx β€” Filter (exclude) on the content of -restrack call stacks. Wildcards (*) are supported.
  • -mc β€” Custom core dump mask (in hex) indicating what memory should be included in the core dump. Please see 'man core' (/proc/[pid]/coredump_filter) for available options.
  • -pf β€” Polling frequency.
  • -o β€” Overwrite existing dump file.
  • -log β€” Writes extended ProcDump tracing to the specified output stream (syslog or stdout).
  • -w β€” Wait for the specified process to launch if it's not running.
  • -pgid β€” Process ID specified refers to a process group ID.

🌸 DESCRIPTION 🌸

ProcDump provides a convenient way for Linux and Mac developers to create core dumps of their application based on performance triggers. And ProcDump is part of Sysinternals. 🫢


lowkey the whole point: you tell it what performance nonsense to watch for, it watches, and it hands you a core dump the moment things get spicy. main character debugging energy, fr fr πŸ’…

and that's the whole vibe check β€” procdump manpage, version 3.4.1, dated 3/17/2025, hanging out in section man(8). go get your dumps bestie, ily, bye πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from