Re: update_char_objects crash

From: Cris Jacobin (jacobin@BELLATLANTIC.NET)
Date: 01/16/98


        I had a similar problem crop up, after having butchered my limits.c
by adding portals, decaying objects, sinking/flying, etc etc.

        What turned out to be going on, was that once an obj was extracted
it didn't exit, just fell down to more checks for other events.  i->in_room
would show up 16369.  Obviously I don't have 16k rooms on my mud (yet).

-Jac of ButterMud


>
>When I do a print i
>(gdb) print i
>$1 = (struct char_data *) 0x2020202
>but, when I do a print *i
>(gdb) print *i
>Cannot access memory at address 0x2020202.
>
>somehow it seems to me my player that got passed somehow got messed.
>any ideas on how I might fix this problem ?
>
>Sorren
>
>
>     +------------------------------------------------------------+
>     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
>     | http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
>     +------------------------------------------------------------+


     +------------------------------------------------------------+
     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     | http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
     +------------------------------------------------------------+



This archive was generated by hypermail 2b30 : 12/15/00 PST