Warzone 2100 Forums

ok - on a newly minted map - i had this crash... and what the heck do you need to read that mdmp file.

lav_coyote25 wrote: ok - on a newly minted map - i had this crash... and what the heck do you need to read that mdmp file.

you need windbg,which is available for download from microsoft's site,you'll have to load the minidump,then load the corresponding symbols(usually the same exe which produced the crash dump),windbg will eventually translate the 'map' into useful debug info/callstack function names.

windbg didn't help for me. I think it cannot read GCC's debug symbols.

DevUrandom wrote: windbg didn't help for me. I think it cannot read GCC's debug symbols.

I kept forgeting about the official windows binaries are not compiled using MSVC express 2005 anymore...though I dont think windows user will be able to use the linux equivalent 'winedbg' to pinpoint the problem under windows...

No he won't be able to do that.
If you know a debug format that is supported by GCC and GDB and that even Windows understands, then you are welcome.

DevUrandom wrote: No he won't be able to do that.
If you know a debug format that is supported by GCC and GDB and that even Windows understands, then you are welcome.

So I'm wondering what do you need to read those minidump files generated by GCC compiled Windows binaries?

winedbg works fine.
If windbg is able to extract the stack, you could also use addr2line from the binutils package to turn it into something meaningful.