Try waiting until the mud is locked, then attach to the process with gdb. This will allow you to see where it's "locking" and diagnose the problem from there. :-)
Tony ----- Original Message ----- From: "Adrian Allen" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, December 16, 2002 4:15 AM Subject: SIGKILL > Sometimes within less than a minute of booting the mud it will just > stop running. I had no idea why until tonight I was using gdb to > debug an area file and after I had the bugs worked out it happened > I remember seeing this one other time using gdb and I know its not > caused by the bug in my area file, having a door reset to a null exit > and then fixing it wouldnt cause this. Its something else. Any ideas? > > > Program terminated with signal SIGKILL, Killed. > > > _________________________________________________________________ > MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. > http://join.msn.com/?page=features/virus > > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom >
