D2X-XL Crash Log Explanation
Posted: Fri Oct 02, 2026 9:08 pm
D2X-XL 2.0: how to send a crash report
When D2X-XL crashes, it now writes a crash report. If you run into a crash, please open a bug report thread here and post it there. It tells me exactly where the program stopped.
Where to find it
The game writes two files into cache\logs inside your D2X-XL folder:
Keep the .pdb file next to the exe
Every exe comes with a pdb file of the same name (e.g. d2x-xl.pdb for d2x-xl.exe). It must stay in the same folder as the exe and must be from the same build. Without it the report only contains addresses instead of function names and line numbers, and I can do very little with it.
You can check this in the "symbols:" line at the top of the .txt file:
is good.
means the pdb is missing or does not belong to this exe.
No report?
A report is only written when the program crashes. If the game freezes, or you end it with the Task Manager, there is none. In that case please send d2x.log and describe what happened.
What a report looks like
When D2X-XL crashes, it now writes a crash report. If you run into a crash, please open a bug report thread here and post it there. It tells me exactly where the program stopped.
Where to find it
The game writes two files into cache\logs inside your D2X-XL folder:
Code: Select all
d2x-xl-crash-<date>-<time>.txt
d2x-xl-crash-<date>-<time>.dmp- If you start the game with -cachedir <dir> or -userdir <dir>, look in <dir>\logs instead.
- If the game crashes right at startup, the files are next to the exe.
- The .txt file. It is small and usually all I need.
- cache\d2x.log from your D2X-XL folder. Copy it before you start the game again: the next start renames it to d2x.log.bak, and the start after that deletes it.
- A short note on what you were doing: mission, level, single or multiplayer, and what happened right before the crash.
Keep the .pdb file next to the exe
Every exe comes with a pdb file of the same name (e.g. d2x-xl.pdb for d2x-xl.exe). It must stay in the same folder as the exe and must be from the same build. Without it the report only contains addresses instead of function names and line numbers, and I can do very little with it.
You can check this in the "symbols:" line at the top of the .txt file:
Code: Select all
symbols: d:\games\d2x-xl\d2x-xl.pdbCode: Select all
symbols: no matching pdb found next to the exe, only addresses availableNo report?
A report is only written when the program crashes. If the game freezes, or you end it with the Task Manager, there is none. In that case please send d2x.log and describe what happened.
What a report looks like
Code: Select all
d2x-xl D2X-XL 2.0.0 crash report
time: 2026-10-02 21:45:43
reason: access violation (0xC0000005)
access: reading address 0x0000000000000010
thread: 25812
symbols: d:\games\d2x-xl\d2x-xl.pdb
call stack:
#00 d2x-xl.exe!CreateExplosion ...\effects\fireball.cpp(344)
#01 d2x-xl.exe!D2Object::Update ...\objects\updateobject.cpp(626)
...