Well, if you are sure it's a command, you can always set all your commands in interp.c to LOG_ALWAYS. That way you can look at the log when it goes into "la la land" and see what the last executed command was.
-V ----- Original Message ----- From: "Cyhawk" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, February 12, 2004 7:39 AM 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 >
