This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

TCL errors

Old posts that have not been replied to for several years.
Locked
User avatar
awyeah
Revered One
Posts: 1580
Joined: Mon Apr 26, 2004 2:37 am
Location: Switzerland
Contact:

TCL errors

Post by awyeah »

Hi,

These are some weird tcl errors I get when I sometimes
restart my bot after a long time, or I restart it immediately
after I have edited its tcls and uploaded them.

They happen sometimes and not always.
Could you please explain me maybe what they mean.

The second one has a long file command and when I
try to break it up into smaller lines using / then it gives
me an error as well.

Code: Select all

<adapter> [17:00] * Last context: tclhash.c/688 []
<adapter> [17:00] * Please REPORT this BUG!
<adapter> [17:00] * Check doc/BUG-REPORT on how to do so.

Code: Select all

<adapter> [03:49] * Last context: tclhash.c/684 [Tcl proc: drone:nick, param:  $_jp1 $_jp2 $_jp3 $_jp4]
<adapter> [03:49] * Please REPORT this BUG!
<adapter> [03:49] * Check doc/BUG-REPORT on how to do so.
<adapter> [03:49] * Wrote DEBUG
<adapter> [03:49] * SEGMENT VIOLATION -- CRASHING!
·­awyeah·

==================================
Facebook: jawad@idsia.ch (Jay Dee)
PS: Guys, I don't accept script helps or requests personally anymore.
==================================
e
egghead
Master
Posts: 481
Joined: Mon Oct 29, 2001 8:00 pm
Contact:

Re: TCL errors

Post by egghead »

awyeah wrote: <adapter> [03:49] * Last context: tclhash.c/684 [Tcl proc: drone:nick, param: $_jp1 $_jp2 $_jp3 $_jp4]
<adapter> [03:49] * Please REPORT this BUG!
<adapter> [03:49] * Check doc/BUG-REPORT on how to do so.
<adapter> [03:49] * Wrote DEBUG
<adapter> [03:49] * SEGMENT VIOLATION -- CRASHING!
[/code]
The error messages you gave are generic and do not help very much in assessing the problem. (Aside from the fact that the process got stuck somewhere around the proc drone:nick).
Locked