Downloads:
447,076
Downloads of v 10.00:
32
Last Update:
12 Nov 2020
Package Maintainer(s):
Software Author(s):
- Mark Russinovich
Tags:
debug process dump sysinternals cli- Software Specific:
- Software Site
- Software License
- Software Mailing List
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
ProcDump
- Software Specific:
- Software Site
- Software License
- Software Mailing List
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
447,076
Downloads of v 10.00:
32
Maintainer(s):
Software Author(s):
- Mark Russinovich
ProcDump
- 1
- 2
- 3
Some Checks Are Exempted or Have Failed
Not All Tests Have Passed
This package was rejected on 28 Nov 2020. The reviewer tunisiano has listed the following reason(s):
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(<name>
_<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
Log in or click on link to see number of positives.
- procdump.10.00.nupkg (76189b5e3ea1) - ## / 64
- Procdump.zip (cf3ece5f2d9b) - ## / 65
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.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
ProcDump 11.0 | 204681 | Thursday, November 3, 2022 | Approved | |
ProcDump 10.11 | 28308 | Thursday, August 19, 2021 | Approved | |
ProcDump 10.1 | 2126 | Wednesday, July 28, 2021 | Approved | |
ProcDump 10.0 | 4275 | Saturday, November 28, 2020 | Approved | |
ProcDump 9.00 | 201328 | Wednesday, May 24, 2017 | Approved | |
ProcDump 8.00 | 2469 | Friday, April 29, 2016 | Approved | |
ProcDump 7.01.0.20160210 | 974 | Wednesday, February 10, 2016 | Approved | |
ProcDump 7.01 | 1274 | Wednesday, September 17, 2014 | Unknown | |
ProcDump 7.0 | 560 | Thursday, May 15, 2014 | Unknown | |
ProcDump 6.0 | 495 | Monday, November 18, 2013 | Unknown | |
ProcDump 5.0.0.1 | 554 | Monday, October 8, 2012 | Unknown |
© Mark Russinovich
This package has no dependencies.
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.
tunisiano (maintainer) on 12 Nov 2020 16:50:37 +00:00:
User 'tunisiano' (maintainer) submitted package.
chocolatey-ops (reviewer) on 12 Nov 2020 17:22:31 +00:00:
procdump has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
tunisiano (maintainer) on 16 Nov 2020 19:50:05 +00:00:
Is there a problem with the verifier? it's stuck for 4 days now.
Thank you.
gep13 (reviewer) on 17 Nov 2020 07:40:44 +00:00:
There is a queue for the package-verifier which is currently being worked through, however, the problem with this package is that it has failed the package-validator. You will need to correct the packageSourceUrl before you will be able to continue.
tunisiano (maintainer) on 17 Nov 2020 17:33:08 +00:00:
Indeed, but currently i'm stuck with a 403 when trying to push the correct version.
Thank you, i'll wait for the list to be worked out.
gep13 (reviewer) on 18 Nov 2020 08:54:17 +00:00:
The 403 error that you are seeing when you attempt a choco push, it is due to the fact that the description element in your nupsec file is too long.
It has to be less than 4000 characters. This error isn't showed correctly within choco.exe, but I can confirm that this is the problem looking at the error logs on the server.
tunisiano (maintainer) on 18 Nov 2020 15:48:21 +00:00:
Ah! Ok, i didn't knew thank you
tunisiano (maintainer) on 20 Nov 2020 07:08:29 +00:00:
FYI, I've cleaned-up the description, but still have the same error, so i'll wait for the verifier.
gep13 (reviewer) on 20 Nov 2020 07:12:40 +00:00:
The package-verifier will not run until the package-validator completes, so you will have to correct the package-validator problem before moving forward.
tunisiano (maintainer) on 28 Nov 2020 16:38:39 +00:00:
Wrong number
Status Change - Changed status of package from 'submitted' to 'rejected'.