How do you read crash.dmp?

Hanover Aldercash on 18/6/2024 at 00:58

zappenduster on 18/6/2024 at 03:58

On (http://www.whoopdedo.org/cgi-bin/dromed.pl) there once was a tool which converted the dump code (and therefore the cause of the DromEd crash).

Try (http://web.archive.org/web/20151014044427/http://www.whoopdedo.org/cgi-bin/dromed.pl)

Hanover Aldercash on 18/6/2024 at 16:42

Is that looking for memory addresses? I don't see any in crash.dmp, just libraries and binary gibberish.

Also, if it matters, I was hoping to understand why my mission is crashing for someone in Thief 2, not DromEd.

vfig on 23/6/2024 at 17:26

Quote Posted by zappenduster

On (http://www.whoopdedo.org/cgi-bin/dromed.pl) there once was a tool which converted the dump code (and therefore the cause of the DromEd crash).

im afraid that is a cgi script, so although the wayback machine has the form in its archive, it wont actually work.

Quote Posted by Hanover Aldercash

you can open the crash dump in ms visual c++ (and some other debuggers) to get more info on the crash. but unfortunately since we dont have .pdb debug symbols for thief exes (or dromed exes either), its often very hard to figure out the cause that way unless you spend some time reverse engineering the assembly code and correlating it with the leaked source code to identify function names and so on.

usually its more effective to ask for a save file and try to recreate the crash yourself from that point, first in-game, and then in dromed.

(a pity that le corbeau did not include pdbs in the newdark releases; but there are good reasons not to)