Skip to content

Conversation

@slurmlord
Copy link
Contributor

This PR adds some practical info about the crash dumps added to the game and how to use them for figuring out crashes.

  • Details the difference between small and full dump files
  • Where dump files are stored
  • What the various components of the file name mean
  • How to find the actual exception that triggered the crash using WinDbg.

The example might a bit on the easy side, so we probably want to augment that with a more extensive case that involves looking at the game object structures etc. I thought this could be a good beginning for someone getting familiar with the code and process, though.

- [Command Line Arguments](switchers_arguments)
- [SafeDiskLauncher](safedisklauncher)
- [CRCDiff](crcdiff)
- [Crash dumps](crashdumps)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wasn't sure where to link it in, so went with the thought of "It's a tool for debugging crashes". Happy to place it elsewhere if suggested.

@slurmlord
Copy link
Contributor Author

Hm, seems like the failed checks need to be manually re-run for this.

@xezon
Copy link
Contributor

xezon commented Jan 3, 2026

It fails with

Asset/Art/dds/dds_files_and_dxt_compression.md:46:121 error MD013/line-length Line length [Expected: 120; Actual: 123]
SourceCode/Builds/build_with_msvc6.md:24:121 error MD013/line-length Line length [Expected: 120; Actual: 123]

@xezon xezon merged commit 7e1fe2e into TheSuperHackers:main Jan 3, 2026
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants