Windows crash dumps DebugDiag vs UserDump

See more:

Windows

Hi, We were previously using UserDump to monitor running Windows applications and generate .dmp files on system exceptions like access violation. This was good but DebugDiag was even better. However DebugDiag has a limit on the number of dump files it produces, to avoid exhausting disk space. The trouble is, we don't know in advance when a production system is going to crash so we just want to monitor every machine indefinitely. There are lots of machines and I can't keep regularly checking them all to see if DebugDiag has reached its limit. A dump file always gets created each night because we have kill scripts for all our apps. UserDump has a feature that keeps only the latest N dump files. Is there any way to configure DebugDiag to do the same? If not, we'll have to revert to UserDump.

No problems with getting decent core dumps for our Linux apps of course! :)