On a Unix system, a core dump is a file with a raw (mostly) copy of a process' current memory image that's written whenever a process does something profoundly illegal, like accessing an inaccessible section of memory with no trap handler that allows recovery or something of the sort. They're handy, because it means you can go and debug a process after the fact, and don't have to be there on the spot to figure out what's going on. Really handy for things that die overnight, or when you're not around, and you don't want the defunct process hanging around until you can attach to it with a debugger.
Does Windows do this? (I know other OSes, like VMS, do *not* do it) If so, how do I enable it? If not, I presume there's some reasonably simple way to attach a debugger to a process that's died. (I hope)
No, I'm not getting turned into a windows programmer, but until I get the Gameboy port of parrot going (or someone slides me an Alpha or Itanium VMS box) it's the only non-Unix platform I've got handy to work with.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
