Re: Interesting Error.

From: Patrick Dughi (dughi@IMAXX.NET)
Date: 05/03/98


>
> >#0  0x8110396 in __libc_free (mem=0x8167aa0) at malloc.c:2736
> >malloc.c:2736: No such file or directory.
> >(gdb) bt
> >#0  0x8110396 in __libc_free (mem=0x8167aa0) at malloc.c:2736
> >#1  0x8110284 in chunk_alloc (ar_ptr=0x88a8070, nb=0) at malloc.c:2673
> >#2  0x80b53c3 in free_char (ch=0x886a3f0) at db.c:2454
>
> How are you able to bt past libc_free?  whenever I have such a crash in
> libc_free and libc_malloc, the stack frame is usually trashed or
> something (no valid backtrace).

        Turned on all the debugging options a while ago. That, and I guess
I'm special. This is also on linux RedHat 5.0 (hurricane), so all the libs
had to be recompiled to work correctly in most cases, but this problem has
only now popped up repetively recently...

> >
> >  Checking player_specials in the second frame looks like this..
> >$1 = (struct player_special_data *) 0x88a8070
>
> Did you check that it is not dummy_mob?
>
        It is a valid player.
                                        PjD


     +------------------------------------------------------------+
     | 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