tcl error in script for..

egghead · Post by **egghead** » Wed Jan 08, 2003 9:51 am

chasm wrote:egghead: there is/was no $t = "t"" on the code. that is wrong.

//chasm

chasm, you are twisting your own arguments and quotation marks. And appearantly it comes to those quotation marks for you before you recognise a "$t == "t"" in a 17 line script.

First you say:

can't seem to find "$t = "t"" in the code.

now you say:

egghead: there is/was no $t = "t"" on the code.

Before you claim something is "wrong", think twice.

chasm · Post by **chasm** » Wed Jan 08, 2003 9:58 am

err, ok.

my bad. i ment that i can't seem to find "$t = "t"" and then you wrote:

< Look again, it is there. Change it to: $t == "t". >

if you check ppslim's code, there was no "$t = "t"" in his code. yeah, i forgot the " before the $t in my last posting. that is my bad.

anyways, i don't see any errors yet. this is promising.

//chasm

egghead · Post by **egghead** » Wed Jan 08, 2003 10:02 am

chasm wrote: anyways, i don't see any errors yet. this is promising.

//chasm

nvm. Let's hope it stays without errors

chasm · Post by **chasm** » Wed Jan 08, 2003 10:08 am

hah, oh my. this -is- funny. i tried to rehash the bot and then..

(read error: eof from client)

i didn't even get to see what the error message was. i tried to start up normally and there was no error. as soon as i rehash, blooop.

hah.

//chasm

chasm · Post by **chasm** » Wed Jan 08, 2003 10:12 am

chasm wrote:hah, oh my. this -is- funny. i tried to rehash the bot and then..

(read error: eof from client)

i didn't even get to see what the error message was. i tried to start up normally and there was no error. as soon as i rehash, blooop.

hah.

//chasm

i tried to unload the rename.tcl script and it rehashed perfectly.

//chasm

ppslim · Post by **ppslim** » Wed Jan 08, 2003 11:19 am

As stated originaly, the script si pretty basic, and doesn't take any consideration for possible issues like this.

The script works by renaming the timer commands. When a timer is needed, the script adds information, that can be used to debug it later.

When you rehash, the script will try renaming the command again.

The issue is this second rehash.

Once the bot is loaded, there should be no need to rehash. The script is designed for use during debugging periods (like this) only, and isn't designed to be used as a everyday script fixer (As it doesn't fix scripts).

If you load the bot without the rename.tcl loaded, and there are no more of these timer errors, then the problems have vanished.

It could take days for them to occur, but I sugest you keep rename.tcl loaded, and do not do a rehash.

chasm · Post by **chasm** » Fri Jan 10, 2003 4:06 am

i sorted this one out too. i installed a new version of the drop and just moved all the important files over.

for now, its seems like it did the trick. no errors for 20 hours.

i'll get back to you when its been running for a couple of days.

thanks for all the help and suggestions!

//chasm

ppslim · Post by **ppslim** » Fri Jan 10, 2003 6:31 am

Out of interest, what version where you running previously.

It may be that it was that old, that needed commands where not provided.

chasm · Post by **chasm** » Fri Jan 10, 2003 6:37 am

i upgraded from version 1.6.12 to 1.6.13, so it is currently running the newest version.

sadly, i got an error about 1½ hour ago. i've restartet the bot with rename.tcl and test.tcl, so i'm waiting for the next one.

//chasm

chasm · Post by **chasm** » Sun Jan 12, 2003 9:38 am

hi again.

finally(?) i got an error. it's been a long while since last time, but now i have a new example with rename.tcl installed:

<botnick> [14:31] Timer error: unset : can't read "uhost": no such variable

does this help?

//chasm

ppslim · Post by **ppslim** » Sun Jan 12, 2003 9:48 am

OK - go to your shell, and change to the bots script directory.

Note type the following

grep "unset \uhost" ./*

This should locate which script this is in.

Now paste the name fo the script, and where you can obtain it from (or upload a copy to some web-space, for use ot see, if it's not in the usual places).

We should be able to help a little more from there.

chasm · Post by **chasm** » Sun Jan 12, 2003 9:49 am

what if it's a windrop?

//chasm

edited: i found 'grep for windows'. trying it out now.

ppslim · Post by **ppslim** » Sun Jan 12, 2003 9:54 am

Click "start" and navigated to "find files and folders".

Simply type "unset uhost" in the sectond text box.

Select borwser, and navigate to the windrops scripts directory, to speed things up.

Now do yoru search.

chasm · Post by **chasm** » Sun Jan 12, 2003 10:16 am

hmm.

now i've tried every possible search-method using wildcards to find anything that matches 'unset uhost', but it looks rather hidden from mr. searchengine too.

there was no hit with 'unset uhost', 'unset*uhost' and all the other methods. i find alof of hits with 'uhost' and 'unset' (of course), but none that match 'unset uhost' etc.

i have done all my searches without the ' chars, yeah. hmpf.

grep for windows == sucks.

//chasm

ppslim · Post by **ppslim** » Sun Jan 12, 2003 10:26 am

Windows search doesn't allow wildcards within this box.