SIGSEG invalid memory reference?

First after ./startup & i get this.

kill Segmentation fault (core dumped)

In the logs I get

Thu Dec 18 07:00:31 2003 :: reading stonebow.are
Thu Dec 18 07:00:31 2003 :: SIGSEG (Invalid memory Reference)
Thu Dec 18 07:00:31 2003 :: VoR Crashed

This is what gdb gives me

Reading symbols from /bin/tcsh...(no debugging symbols found)...done.
Reading symbols from /lib/libtermcap.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libtermcap.so.2
Reading symbols from /lib/libcrypt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /lib/tls/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libnss_dns.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_dns.so.2
Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libresolv.so.2
0xffffe002 in ?? ()
(gdb) bt
#0 0xffffe002 in ?? ()
#1 0x420279c4 in __sigpause () from /lib/tls/libc.so.6
#2 0x08064177 in strcpy ()
#3 0x080640c4 in strcpy ()
#4 0x0806649c in strcpy ()
#5 0x08066652 in strcpy ()
#6 0x0804cea8 in strcpy ()
#7 0x0804aff0 in strcpy ()
#8 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6

never ever seen that... also in comm.c where SIGSEG is grepped at it shows this

void sig_seg( int sig )
{
log_string("SIGSEG (Invalid memory Reference)");
tell_all( sig );
}

any ideas?

Something is going wrong with reading the area stonebow.are... the back trace doesn't seem to be terribly useful, so go through the functions that handle reading area files. It also seems that strcpy is called before the crash, so look for places where strcpy is called.

Perhaps the area file is corrupt somehow, or perhaps the code is broken, or both. :)

One other thing to consider - the crash handler in that code might be boogering your results. I'd suggest at least disabling that code and trying again to see if you get a useful core from it.

And compile with debug symbols enabled.