D2X-XL Crash Log Explanation

[Adminion]

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:

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.

What to send

1. The .txt file. It is small and usually all I need.
2. 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.
3. A short note on what you were doing: mission, level, single or multiplayer, and what happened right before the crash.

Keep the .dmp file, but only send it if I ask for it.

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.pdb

is good.

Code: Select all

symbols:   no matching pdb found next to the exe, only addresses available

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

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)
  ...

[Sirius]

In case it helps for those freezes: In Windows 10/11, you can create a memory dump of a running process from Task Manager by right-clicking on it and selecting "Create memory dump file".
I'm not sure how you'd do this in Linux - could be distro-dependent - but there's probably some way.

[Adminion]

Good hint!

Actually D2X-XL should produce this crash dump with a stack trace when it crashes, so you shouldn't need to create a crash dump via Windows, but you never know when it might be needed anyway.