> Unfortunately I can't be much help with the freeze, but on a side note > about the sighandler code, when you use a sighandler it is very rare > that you will get a core file as the code handles the signal and does a
Yeah, you can get a core with a signal handler. I do it all the time... fortunately... or unfortunately ;) > Now, here's the big problem. After the mud was restarted again, I was > watching the process in 'top'.. the cpu % would drop to 0.00% and the mud > would just freeze up there. Usually whenever it would get stuck in a loop, > the process cpu would skyrocket, but here it is down at nothing, and the > mud is totally frozen. And it does this for at least 2-3 hours straight.. > every couple minutes. When the MUD freezes, you can attach gdb to the process and see what it's doing. Or...kill it with a segfault and it'll drop a core like it had crashed, then you can do your thing. --Palrich.
