Usually, when I get an error such as this, it is from a mem leak or just plain using bad memory (a mis-pointed pointer). What you should do is start up your mud in GDB and start walking through it from the beginning. (since you know how to do a backtrace, I'm assuming you know how to use 'step' and 'next' to some effectiveness. Just next your way over the reliable low-level functions (fread_string, and such) while stepping into other functions that OLC possibly tampered with (load_mobile for instance), and let us know exactly where your mud goes from smoothrunning to kerplunk in ??.
Ammaross Danan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Mcdougal Sent: Friday, April 01, 2005 6:53 PM To: [email protected] Subject: OLC 1.8 related segfaults? 0xffffe002 in ?? () (gdb) bt #0 0xffffe002 in ?? () #1 0x0805fc91 in main (argc=2, argv=0x0) at comm.c:422 #2 0x42015704 in __libc_start_main () from /lib/tls/libc.so.6
