I just started playing around with procdump and and I want to have a full dump of an application when an unhanded second chance exception occurs.
According to the documentation I run it likes this:
procdump.exe -ma -e -x C:\CrashDumps C:\Code\CrashApp\CrashApp\bin\Debug\CrashApp.exe
CrashApp.exe
is a simple console application that throws an exception when started.
This is the output I get:
ProcDump v7.0 - Writes process dump files
Copyright (C) 2009-2014 Mark Russinovich
Sysinternals - www.sysinternals.com
With contributions from Andrew Richards
Process: CrashApp.exe (6516)
CPU threshold: n/a
Performance counter: n/a
Commit threshold: n/a
Threshold seconds: 10
Hung window check: Disabled
Log debug strings: Disabled
Exception monitor: Unhandled
Exception filter: *
Terminate monitor: Disabled
Cloning type: Disabled
Concurrent limit: n/a
Avoid outage: n/a
Number of dumps: 1
Dump folder: C:\CrashDumps\
Dump filename/mask: PROCESSNAME_YYMMDD_HHMMSS
Press Ctrl-C to end monitoring without terminating the process.
CLR Version: v4.0.30319
[23:54:51] Exception: E0434F4D.System.Exception ("Hello World")
Unhandled Exception: System.Exception: Hello World
at CrashApp.Program.Crash(String message) in c:\Code\CrashApp\CrashApp\Program.cs:line 18
at CrashApp.Program.Main(String[] args) in c:\Code\CrashApp\CrashApp\Program.cs:line 13
[23:54:52] The process has exited.
[23:54:52] Dump count not reached.
As you can see he reports an unhanded exception but doesn't create a dump.
What am I doing wrong here?
Open Start. Search for Command Prompt, right-click the top result, and select the Run as administrator option. Type the following command to navigate to the folder containing the ProcDump tool and press Enter: cd C:\Users\username\Documents\Procdump.
Since .net
tag is present, I suspect that you are monitoring managed process. If so, then add -g
command line option and procdump will work as you expect.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With