How to analyze Crashdump's?

[[Fx]GhOsT]

That's a question i always had.

First of all, there are some *.dmp extension files, is it possible to open them? Isn't it private?

Is very hard to analyze?

And how I can start? For example this crash.

** -- Unhandled exception -- ** 
Version = 1.1-unstable-2143.0.000 
Time = Sun Dec 26 13:26:21 2010 
Module = deathmatch\client.dll 
Code = 0xC0000005 
Offset = 0x00047490 
  
EAX=00000000  EBX=0022F928  ECX=0DBCB928  EDX=00000000  ESI=00000000 
EDI=00000000  EBP=0022F928  ESP=0022F878  EIP=0DB47490  FLG=00010202 
CS=001B   DS=0023  SS=0023  ES=0023   FS=003B  GS=0000 
  
** -- End of unhandled exception -- ** 
  

How can I know where the game crashed? To try to ellaborate a fix/sollution? For now i just understand that there was something wrong in "Client.dll" and the time

[lil Toady]

You can not analyze dumps without compilation symbols which are private.

The 'Code' is obviously the error code, this one means access violation.

Offset - pretty obvious as well, i guess.

And the stuff under that is the registers and flags

http://en.wikipedia.org/wiki/X86#Addressing_modes

For somebody who's not familar with programming and mta sources those things wont help much. And as a warning, don't make any assumptions over crashes by what it says in the 'Module', it doesn't always mean that the problem is in that module, it's just the one that's thrown the exception.

[ryden]

Unless you compiled that MTA client, you'll have it hard to analyze it. Ask ccw for the debugging symbols, if he's sharing. Specify the version and revision of your client.