YGGverse
/
xash3d-fwgs
mirror of https://github.com/YGGverse/xash3d-fwgs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Xash3D FWGS engine.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2538 Commits
6 Branches
2 Tags
16 MiB
 
 
 
 
Tree: 182d8edb42
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '182d8edb42'
${ noResults }
xash3d-fwgs/Documentation/debugging-using-minidumps.md

1.4 KiB
Raw Blame History

Debugging your mod using minidump files (Windows only)

Minidump files is awesome instrument for debugging your mod after it's being released, or for catch specific crashes which are presented only in one specific configuration, but doesn't happens in other configurations or even on developer machine. It contains a lot of information useful for debugging, and therefore it size is not so small: around hundreds or even thousands of megabytes. But this is not a problem, since minidump files compresses very effectively using common algorithms. There are short algorithm, explaining how to use this debugging instrument:

  1. User starts your mod with -minidumps startup parameter
  2. Finally, crash happened on user's machine, and minidump file being written. This file has .mdmp extension and located in same folder, where mod folder located
  3. User packs this minidump file to .zip/.7z archive, and somehow sends it to developer
  4. Developer just opens minidump file in Visual Studio, then a virtual debugging session is opened and now reasons of crash is pretty easy to detect: you can see call stack, local function variables and global variables, information about exception and a lot of other information

You can find more information about minidumps in this awesome article.