if you're using ivan's olc like lots of places out there, there shouldn't be
any number that needs to be upped, because the save area routines run through a
linked list until they hit NULL at the end of it, vs. an array where you'd have
to raise the max index value to include new areas... you should first look at
where it's crashing, randomly in one of the many area files? or always at the
same point in the same file... then you can try to either take that filename
out of the area list when you load the mud, do an asave world and see if it's
crashing in the next file that was in the list (showing that it seems to be
having a problem with say, the 13th element of the list every time), or whether
it goes through completely or crashes in some other random file... but your
best bet is going to be to run the mud in gdb and do an asave world and see
what it says when it autobreaks on the sigsegv signal... make sure you've got a
backup of all your areas...
wavewave
Richard Lindsey.
-----Original Message-----
From: Cyhawk [mailto:[EMAIL PROTECTED]
Sent: Sun 3/28/2004 4:01 AM
To: [email protected]
Cc:
Subject: asave area
Hey all, quick question. Some areas crash on saving, and croupt the file
(ie stop writing 1/2 way through)
So im thinking some number somewhere needs to be upped. Since GDB is no
help in this matter, anyone
have any ideas on which number it is and where its located? =)
-Thri
--
ROM mailing list
[email protected]
http://www.rom.org/cgi-bin/mailman/listinfo/rom
