Bah... Jason has graciously stuck me with a much needed cattle prod. My lack of consistent crashes is probably due to my good luck that ch->class was usually viable (without being explicitly set). Sorry for the list spam :(
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 13, 2002 2:47 PM To: [email protected] Subject: Wierd new_char() crash Hey list, According to my changelog, I haven't done anything that should cause any crashes regarding new_char(). However, all of a sudden my poor little guy goes boom after it's booted up. Specifically, it's going bang trying to set ch->max_hit = class_table[ch->class].hp_base... and the problem is of course that ch->class is some odd number which it shouldn't be at all. My question is how does a totally new CHAR_DATA *obj get allocated incorrectly? I've checked to make sure it is really alloc_perm'ing *ch and not using char_free. I must confess I'm not as up on my memory management as I probably should be, but the thing doesn't give me any problems with the thousands of ch's being made at boot... Steve -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
