*** Crashes ***

Crashes when developing something as complex as a mudlib in a language like
C are pretty inevitable. Because of this there are some crash debug variables
in the code which will narrow down the possible areas at fault. The variables
are com_stage and event_stage which are set with various values depending on
what portion of the code the main server (main.c) is in. 

If the mud crashes either the event stage or com_stage will be printed plus
if appropriate the object, room or region the mud was executing the code of
at the time.

Eg: 
If the mud crashes while executing the event code of object sheep you would 
get "(ES = 5, OBJ = sheep)"
Similarly if it crashed whilst executing the command code in room 13 you would
get "(CS = 1, RM = 13)"

The variables used to print the object name , room or region are 
curr_obj->name, this_room and this_region.

com_stage (CS) is set in the exec_com() function and events_stage (ES) in the 
do_events() function. I suggest you look through the code to get an idea of how
F
things work.

