Eriol wrote:
Is it actually possible to put that stack back into some type of debugging tool and reconstruct it? If so, your code-foo is better than mine, and I'd love to know what tool you're using for that.
I don't even see the code anymore. I just see blond, brunette, redhead...
Ok, in all seriousness, we basically keep the .map and .cod compiler/linker output files for like the last 100 builds or something crazy. I just look at the callstack (and if that doesn't work or the callstack is nonsense I basically have to read the stack dump by hand) and figure out what line of code is referenced by the callstack. Sometimes I have to pick out data from the stack dump, but that doesn't happen too often. So, as far as tools go, I use my Brain? and some text files
For client crashes internally we just drop a minidump file that Visual Studio can read.
Yes, I am a geek. /flash_geek_badge
LINK