Save a Memory Dump for debugging Crashes

DarkRadiant or TheDarkMod crashed? If you don't want that to happen again, you need to help the team to debug this malfunction
You can do this by dumping process memory to a file, which can then be used by developers to debug and inspect the application's state at the point in time it crashed.

If a crash is reproducible, it might be enough to describe the exact steps that lead up to the fault and file a bug report on the bugtracker.
But more often than sometimes crashes occur out of seemingly nothing and are barely reproducible, and in this case a saved memory dump is even more valuable for debugging purposes.

In principle, recording memory dumps is not limited to crashed applications.
It is possible to record memory dump of alive process, although in most cases such dump would be useless.

Windows

Enable Memory Dumps

When application crashes, it usually shows a dialog like this:

If you don't get that window showing up for you, please check the WER flag in registry editor:

• Run the Registry Editor
• Find path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
• Create DWORD (32bit) key with name DontShowUI and value 0

See alternative method here: https://superuser.com/a/1349113

Record Memory Dumps

1. When the dialog appears, keep that window open, don't close that dialog, instead open your Task Manager.
   To open the Task Manager, press Ctrl + Shift + Escape.
   Another way is to hit Windows + R and type "taskmgr" and click OK.
2. In the Task Manager, switch to the Processes tab and locate the program which crashed (DarkRadiant.exe, TheDarkModx64.exe or tdm_installer.exe).
   It should be in that list since you still have the "XXX has stopped working" dialog open in the background.
3. Now right-click the line with the name of the crashed program and select "Create dump file":
4. It will work a bit and then show you something like this: "The file has been sucessfully created. The file is located at: location"
5. Open Windows Explorer and head to the location indicated in the dialog.
   Note that you can mark and copy the location from that dialog using your mouse, so you don't have to type it in entirely.

Compress and upload the dump

Depending on what you had opened in DarkRadiant or what FM you loaded in the game itself, the .dmp file might end up very large,
so it's best to compress it by right-clicking it and selecting "Send to..." > "Compressed (zip) folder".
(Or use 7-zip to compress the file)
Upload that folder to some place in the web, and please go to the forums to tell the devs about your crash dump.

Thanks for your time,
we know that recording and uploading crash dumps might be tedious,
but without we really can't do much about the crash, so your help is appreciated!

Debugging / Analysis

Coders might want to check out the article on analyzing a memory dump.

Record Memory Dumps automatically (alternative approach)

When the "darkradiant has stopped working" popup doesnt appear, when the program crashes,
then is possible to enable automatic saving of crash dumps,
This way is not recommended since it is more complicated to setup.
It is also described in Windows User-Mode Dumps.

1. Press Windows-key + R, type in "cmd", and press Ctrl+Shift+Enter to run it with admin rights.
2. A black window of console will appear. Check the title bar and make sure it is running with administrator rights.
3. Execute the following commands in the console (copy/paste them with Ctrl+C / Ctrl+V):
4. reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\TheDarkModx64.exe" /t REG_SZ /v "DumpFolder" /d "c:\temp\CrashDumps"
5. reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\TheDarkModx64.exe" /t REG_DWORD /v "DumpCount" /d "0x1"
6. reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\TheDarkModx64.exe" /t REG_DWORD /v "DumpType" /d "0x2"
7. reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\TheDarkModx64.exe" /t REG_DWORD /v "CustomDumpFlags" /d "0"
8. net start WerSvc
   (if there is a windows service named "Windows Error Reporting Service")
9. Close the console, you don't need it anymore.

Now you can run TDM as usual (run executable TheDarkModx64.exe).
If it crashes, a dump will be recorded and saved at C:\temp\CrashDumps.

After this you need to disable automatic saving of memory dumps for TheDarkModx64.exe:

1. Press Windows-key + R, type in "cmd", and press Ctrl+Shift+Enter to run it with admin rights.
2. A black window of console will appear. Check the title bar and make sure it is running with administrator rights.
3. Execute the following commands in the console (copy/paste them with Ctrl+C / Ctrl+V):
4. reg delete "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\TheDarkModx64.exe"

Alternatively, you can add/remove registry keys directly in Registry Editor if you like. In this case, restart Windows instead of starting WerSvc service.

Linux

Record with GDB

Make sure GDB is installed. Usually it is installed by default.

1. Run the game under GDB: gdb ./thedarkmod.x64
2. Within GDB, type run and hit Enter to start the program.
3. When the game crashes, gdb will most likely break.
4. Record core dump with a command: generate-core-file
5. The dump should be in the current directory, usually named like core.27372.

Note that core dumps are pretty large, but they compress well. Make sure to put it into zip/gz/whatever before uploading.

Unfortunately, sometimes core dump alone is not enough to inspect the crash on the other machine. A developer might need some system binaries in order to properly decipher stack trace. The following libraries are known to be necessary sometimes:

• libc
• libpthread
• libthread_db

These files are usually named something like libpthread-2.26.so, libc-2.26.so, libthread_db.so.1 and are located in /lib/x86_64-linux-gnu. Beware of symlinks! The developer needs the target file with real contents.

See also: "Mission downloader issue" on the forum