Re: {CIRCLE][ASCII] same 8 character problems with a twist

From: George Greer (greerga@circlemud.org)
Date: 06/17/99


On Thu, 17 Jun 1999, John Hines wrote:

>0x806ca7b in game_loop (mother_desc=0) at comm.c:859

Ponder, why is your 'mother_desc' set to 0? Did you close
stderr/stdin/stdout before creating the socket?

>859             GET_WAIT_STATE(d->character) -= (GET_WAIT_STATE(d->character) > 0);

d->character is probably NULL.

>(gdb) print d
>$1 = (struct descriptor_data *) 0x83c7668
>(gdb) print d->character
>$2 = (char_data *) 0x83c9928

Hm, worse, it's a valid pointer.

>(gdb) print *d
>$3 = {descriptor = 6, host = "ppp209.grnco.net", '\000' <repeats 14 times>,
[...]
>  large_outbuf = 0x0, input = {head = 0x0, tail = 0x83cccc0},
>    character = 0x83c9928, original = 0x0, snooping = 0x0, snoop_by = 0x0,
>  next = 0x0, olc = 0x0, storage = 0x0}

Don't know off-hand if NULL 'head' and valid 'tail' is ok.  I'm guessing
it's not a problem.

>(gdb) print *d->character
>$4 = {pfilepos = 0, nr = -1, in_room = 763, was_in_room = -1, wait = 0,

And 'd->character' actually points to valid memory too.

>Am i correct in thinking that this is pointing to load_char?
>Seems that login (last) and birth are the same...

If it's a new character, that'd be normal.

>There are a bunch of 0x0 in there (being not created) this will take
>me forever to figgure out...

Some are entirely normal.


From the above, don't see why.  Perhaps the character had been free()'d
previously.

--
George Greer            | CircleMUD Snippets
greerga@circlemud.org   | http://developer.circlemud.org/snippets/


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



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