 | | | asave changed segment fault | asave changed segment fault 2003-11-25 - By Cyhawk
Back
Ok i told my self i need to cool it on the rom mailing list for small
things.. but this one is baffling and pretty serious
whenever asave changed is issued, i get (gdb output)
Program received signal SIGSEGV, Segmentation fault.
game_loop_unix (control=6) at comm.c:789
789 d_next = d->next;
To my knowledge, i have yet changed comm.c
specific snip its refering to is..
/*
* Process input.
*/
for (d = descriptor_list; d != NULL; d = d_next)
{
d_next = d->next;
d->fcommand = FALSE;
if (FD_ISSET (d->descriptor, &in_set))
{
if (d->character != NULL)
d->character->timer = 0;
if (!read_from_descriptor (d))
{
FD_CLR (d->descriptor, &out_set);
if (d->character != NULL && d->connected == CON_PLAYING)
save_char_obj (d->character);
d->outtop = 0;
close_socket (d);
continue;
}
}
inside of game_loop_unix
This only happened after i added a new spec (only changes to special.c) I
doubt this could of caused it.
Any help is always appreciated =)
-Thri
--
ROM mailing list
ROM@(protected)
http://www.rom.org/cgi-bin/mailman/listinfo/rom
Earn $52 per hosting referral at Lunarpages.
|
|
|