Debugging Files

There are 3 places you can find information on what went wrong:

1. ~/testmud/DMS.ERR
2. ~/testmud/lib/logs/log/debug
3. ~/testmud/core.*

1. ~/testmud/DMS.ERR

When the mud is loading, all of the output is written to the DMS.ERR file. By looking at this file you can tell where the reboot stopped, and therefor what caused the failure. This is the first place you should look.

Example

2. ~/testmud/lib/logs/log/debug

The debug file prints slightly more information about what went wrong. Generally it just complains about rooms flagged as "single file" that don't have 2 exits. This is the second place you should look.

Example

3. ~/testmud/core.*

Anytime the game crashes it writes out a core that shows you the stack of functions that were executing. Find the most recent core by typing,
ls -lt core.* | head

And then edit the core with
gdb dms core.<#>

Some commands you can use are,

• where
• tb
• frame #
• list #

Example