Crash when digging

[xoft]

and all the .pdb files right? or is that different with linux?

Linux packs all the PDB files' contents into the executable (so the "exe" for Linux is huge - I think about 30 MiB). One can also strip the information altogether, then the "exe" is smaller but the debugging info is lost.

How is possible to find an error in 116mb of code?

The crashdump contains a complete snapshot of the server's memory, including what instructions were just being executed. So usually I can see "I called function A, that called function B with these parameters, which called function C with these parameters, which .... which called function Z that crashed".

If you did the post-mortem analysis, using the gdb and its bt command, that's exactly what I'm doing.

So then I know to focus my attention to that chain of function calls, and coupled with the error message, I can usually figure out what's going on. The more difficult part is determining, why it's going on