[crossfire] Code cleanlieness and server stability

[Alex Schultz]

I have a hunch this is one of those cases where the object is modified 
after creation. I'm not really sure, but perhaps it's something similar 
to the old bug with spellbooks losing their spell when thrown (which is 
a bug that I think has been fixed).

Mark Wedel wrote:

>  One thought I've had, which would use more memory, is to use the glibc 
>backtrace() functionality and add code to get_object() that stores away the 
>backtrace.  Thus, when we get an object in a funky state, we can hopefully see 
>how the object was created (calling structure).  However, this still doesn't 
>catch the cases where the object is modified after creation, etc.
>