Another thing you can try is using gdb to detect the infinite loop... if you don't know how to attach it to a running process, just go to the directory that your executable is in (we'll call it src and rom for defaults), and type ps -ux, this'll bring up the list of things that are currently running on your account, get the pid of the rom job and (assuming it's 5571) you'd type this:
gdb ./rom 5571 this will load gdb and attach it to the running mud process... then just go about testing it like you have been normally when you found the mud hanging up, and the next time it hangs up, just flip over to your shell login and you should see that gdb broke it on the line that's causing the infinite loop... Richard Lindsey Network Administrator INTERA, Inc. 9111A Research Blvd. Austin, TX 78758 (512) 425-2006 [EMAIL PROTECTED] -----Original Message----- From: Cyhawk [mailto:[EMAIL PROTECTED] Sent: Thursday, February 12, 2004 6:40 AM To: [email protected] Subject: a loop i can't find Hey all. No im not asking for long range debugging on this one ;) Ok, heres the problem, somewhere, sometime, some command is going into a loop. (almost certin its a command, due to the fact i have 3 test ports running, both have been up for 72+ hours) First, is there any way to detect a loop and stop it before it happens? Second, is there an easy way to log everything short of #ifdef DEBUG in every function? (I knew i should of done this from the start) Third: Any other option avaible to me? =) -Thri -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
