> However, poking around there I am unable to find any way of disabling these
> massive files.

You're right, I thought there was a "disable" option, but I don't see one. 
There should be (even though I'd recommend against using it).

> Nor any particular explanation of why the files would be so
> huge. Plain text error reports can't possibly stretch into gigabyte size,
> can they? The few that are listed there seem to contain less text than this
> email.

The big dump files contain copies of the contents of large hunks of memory. The 
developers of the failing program can load them up in their debuggers and see 
exactly what's going on, i.e, what the
program was doing when it crashed, the contents of variables, etc. That's what 
makes it possible to isolate and fix the error. 

Earlier this week I got a crash dump from an error we'd never seen before (and 
the program I work on has many millions of users). I was able to understand and 
fix the problem in under 10 minutes, and
as of the next release in a few weeks, anyone who experiences the same issue 
will immediately get a notification that it's been fixed and how to get an 
update. 
 
> And aren't those covered under the 'dump' files under
> System>Advanced>debugging info?

I don't believe so. I think those are the blue screen dumps.


*************************************************************************
**  List info, subscription management, list rules, archives, privacy  **
**  policy, calmness, a member map, and more at http://www.cguys.org/  **
*************************************************************************

Reply via email to