ProcDump 3.5.1

Add support for RHEL10, Debian 13, Ubuntu 26.04, Fedora 43 and updated dependencies

ProcDump 3.5.0

Changes:

• Add logging for missing symbols in restrack callstacks (#293)
• Fix dotnet socket PID matching to prevent conflicts between processes (#292) [ #283 ]
• Updating trigger docs and removing unused condition in Monitor (#280)
• Add manual trigger support for restrack snapshots (#279)
• Use prctl syscall to enable ptrace + replace stress-ng with custom stress cpu/mem code (#290)

ProcDump 3.4.1

Changes:

• Removes the ':' separator for the date/time section of the generated core dump filename, aligning across operating systems (#269)
• Monitor: remove useless variables (#267)

ProcDump 3.4.0

Changes:

• Add ARM64 support (#265)
• Fix clang compilation errors due to variable length arrays (#264)

ProcDump 3.3

Changes:

• Enable diagnostics logging to go to either syslog or stdout (#242)
• Procdump requires su even when the user running procodump is the same as the user running the target process (#243)
• Procdump -restrack does not work in a containerized environment (#244)
• -restrack calloc and reallocarray sizes are incorrect (#245)
• Enable eBPF tracing when -log switch is specified (#246)
• Enable restrack without specifying triggers (#248)
• Race condition during exit where RestrackThread can leave a mutex orphaned due to thread cancellation (#249)

ProcDump 3.2

Changes:

• Add mmap/munmap to resource tracking (#230)
• Fix gc generation configuration printout (#229)

ProcDump 3.1

Changes:

• c368649 Add support for multiple signals (-sig) and specifying core dump contents (-mc) (#226)
• 3df0ee2 Cleanup a lots of unused variables (#223)
• daa2621 Doc: How to implement a trigger (#220)

ProcDump 3.0

Changes:

• Adds memory leak tracking and reporting (-restrack)

ProcDump 2.2

Changes:

• Add Azure Linux package and install instructions (#210)
• Fixing some leaks in src/Monitor.c code (#204)

ProcDump 2.1

Changes:

• Fix crash in monitored .NET process when an exception does not have an exception message (#201)
• Add thread ID to logging (#200)