I'd suggest leaving the mud running in gdb... when it segfaults, gdb should catch it and show you where, then you can check the info on some of the variables in use and see why it's crashing... if you don't know how to attach gdb to the mud when it's already running just go to your shell, ps -ux, get the mud's pid, and type
gdb ./src <pid> continue and just let it run it's natural course... Richard Lindsey -----Original Message----- From: Matthew Martin [mailto:[EMAIL PROTECTED] Sent: Monday, May 10, 2004 10:04 AM To: [email protected] Subject: Segmentation Fault I keep getting this message in my shell. No crashes, no core dumps, just a Segmentation fault, mud kills, then restarts. I started logging all of the processes running in update.c to see where the Seg fault was coming from, but after perusing the logs, it doesn't seem to be occuring in a specific location...Sometimes it kills on mob_update, sometimes on obj_update, but it's not reproducable, at least, not that I've been able to find. Any of you guys have an idea for me? _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.com/go/onm00200415ave/direct/01/ -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
