Downloads:

26,807

Downloads of v 9.00:

21,451

Last Update:

24 May 2017

Package Maintainer(s):

Software Author(s):

  • Mark Russinovich

Tags:

debug process dump sysinternals cli

ProcDump

9.00 | Updated: 24 May 2017

Downloads:

26,807

Downloads of v 9.00:

21,451

Maintainer(s):

Software Author(s):

  • Mark Russinovich

ProcDump 9.00

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install ProcDump, run the following command from the command line or from PowerShell:

>

To upgrade ProcDump, run the following command from the command line or from PowerShell:

>

To uninstall ProcDump, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade procdump -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade procdump -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure procdump installed
  win_chocolatey:
    name: procdump
    state: present
    version: 9.00
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'procdump' do
  action    :install
  version  '9.00'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: procdump,
    Version: 9.00,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller procdump
{
   Name     = 'procdump'
   Ensure   = 'Present'
   Version  = '9.00'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'procdump':
  provider => 'chocolatey',
  ensure   => '9.00',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install procdump version="9.00" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 01 Nov 2019.

Description

ProcDump is a command-line utility whose primary purpose is monitoring an application for CPU spikes and generating crash dumps.

Command line usage

procdump [-a] [[-c|-cl CPU usage] [-u] [-s seconds]] [-n exceeds] [-e [1 [-b]] [-f <filter,...>] [-g] [-h] [-l] [-m|-ml commit usage] [-ma | -mp] [-o] [-p|-pl counter threshold] [-r] [-t] [-d <callback DLL>] [-64] <[-w] <process name | service name | PID> [dump file] | -i <dump file> | -u | -x <dump file> <image file> [arguments] >] [-? [ -e]

-a
Avoid outage. Requires -r. If the trigger will cause the target to suspend for a prolonged time due to an exceeded concurrent dump limit, the trigger will be skipped

-b
Treat debug breakpoints as exceptions (otherwise ignore them)

-c
CPU threshold at which to create a dump of the process

-cl
CPU threshold below which to create a dump of the process

-d
Invoke the minidump callback routine named MiniDumpCallbackRoutine of the specified DLL

-e
Write a dump when the process encounters an unhandled exception. Include the 1 to create dump on first chance exceptions

-f
Filter the first chance exceptions. Wildcards (*) are supported. To just display the names without dumping, use a blank ("") filter

-g
Run as a native debugger in a managed process (no interop)

-h
Write dump if process has a hung window (does not respond to window messages for at least 5 seconds)

-i
Install ProcDump as the AeDebug postmortem debugger. Only -ma, -mp, -d and -r are supported as additional options

-l
Display the debug logging of the process

-m
Memory commit threshold in MB at which to create a dump

-ma
Write a dump file with all process memory. The default dump format only includes thread and handle information

-ml
Trigger when memory commit drops below specified MB value

-mp
Write a dump file with thread and handle information, and all read/write process memory. To minimize dump size, memory areas larger than 512MB are searched for, and if found, the largest area is excluded. A memory area is the collection of same sized memory allocation areas. The removal of this (cache) memory reduces Exchange and SQL Server dumps by over 90%

-n
Number of dumps to write before exiting

-o
Overwrite an existing dump file

-p
Trigger on the specified performance counter when the threshold is exceeded. Note: to specify a process counter when there are multiple instances of the process running, use the process ID with the following syntax: "\Process(&lt;name&gt;_<pid>)\counter"`

-pl
Trigger when performance counter falls below the specified value

-r
Dump using a clone. Concurrent limit is optional (default 1, max 5). CAUTION: a high concurrency value may impact system performance

  • Windows 7, 8 : Uses Reflection. OS doesn't support -e.
  • Windows 8.1+ : Uses PSS. All trigger types are supported.

-s
Consecutive seconds before dump is written (default is 10)

-t
Write a dump when the process terminates

-u
Treat CPU usage relative to a single core (used with -c). As the only option, Uninstalls ProcDump as the postmortem debugger

-w
Wait for the specified process to launch if it's not running

-x
Launch the specified image with optional arguments. If it is a Store Application or Package, ProcDump will start on the next activation (only)

-64
By default ProcDump will capture a 32-bit dump of a 32-bit process when running on 64-bit Windows. This option overrides to create a 64-bit dump. Only use for WOW64 subsystem debugging

-?
Use -? -e to see example command lines


tools\chocolateyInstall.ps1
$packageName = 'procdump'
$url = 'https://download.sysinternals.com/files/Procdump.zip'
$checksum = '9e089b3f25a85c58f901094e4126412bbef480bd7baef2a9039bdef328bf5baa'
$checksumType = 'sha256'
$url64 = "$url"
$checksum64 = "$checksum"
$checksumType64 = "checksumType"
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
Install-ChocolateyZipPackage -PackageName "$packageName" `
                             -Url "$url" `
                             -UnzipLocation "$toolsDir" `
                             -Url64bit "$url64" `
                             -Checksum "$checksum" `
                             -ChecksumType "$checksumType" `
                             -Checksum64 "$checksum64" `
                             -ChecksumType64 "$checksumType64"
Write-Verbose "Accepting license..."
$regRoot = 'HKCU:\Software\Sysinternals'
$regPkg = 'ProcDump'
$regPath = Join-Path $regRoot $regPkg
if (!(Test-Path $regRoot)) {New-Item -Path "$regRoot"}
if (!(Test-Path $regPath)) {New-Item -Path "$regRoot" -Name "$regPkg"}
Set-ItemProperty -Path "$regPath" -Name EulaAccepted -Value 1
if ((Get-ItemProperty -Path "$regPath").EulaAccepted -ne 1) {
  throw "Failed setting registry value."
}

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
ProcDump 8.00 2304 Friday, April 29, 2016 Approved
ProcDump 7.01.0.20160210 829 Wednesday, February 10, 2016 Approved
ProcDump 7.01 1081 Wednesday, September 17, 2014 Unknown
ProcDump 7.0 402 Thursday, May 15, 2014 Unknown
ProcDump 6.0 346 Monday, November 18, 2013 Unknown
ProcDump 5.0.0.1 394 Monday, October 8, 2012 Unknown

Program

Package

  • Automatically built and uploaded by dtgm

This package has no dependencies.

Discussion for the ProcDump Package

Ground Rules:

  • This discussion is only about ProcDump and the ProcDump package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or ProcDump, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus