Raymond Hicks wrote:

> I have had a problem with running infobot after my recent cvsup to
> current.  I have heard that there is a problem with the newer perl
> version.. is this a result of that?  Here is error:
> deepwoods# Missing braces on \N{} at ./src/Irc.pl line 131, near ">>> $b"
> Missing braces on \N{} at ./src/Irc.pl line 133, near ">>> $b"
> Missing braces on \N{} at ./src/Irc.pl line 152, within string
> Compilation failed in require at ./infobot line 39.
> BEGIN failed--compilation aborted at ./infobot line 42.

Welp, hard to help you here since there isn't any version info for the 
infobot, but.. I am succesfully running a blootbot 1.0.0pre4 (infobot 
derivative) in -CURRENT, and haven't seen any such problem. If there is 
indeed a problem with the new perl (which is in -STABLE too I believe), 
I'm sure it's been fixed by now. Just about every new box that gets 
rolled out with perl comes with 5.6.0 nowadays..

The only problem I've seen, since ~October? is the ocassional exec bug 
from backticked execs in perl from the infobot. In this case, it was for 
ps/tail to find out it's current memory. We just commented out the 
memory usage check and perl no longer core dumps.

Just for reference, here are two of the perl core dumps from November 
(libc actually!)

#0  0x2819e1b8 in kill () from /usr/lib/libc_r.so.5
#1  0x281eb652 in abort () from /usr/lib/libc_r.so.5
#2  0x281b6095 in _thread_exit () from /usr/lib/libc_r.so.5
#3  0x281af4ba in _pq_remove () from /usr/lib/libc_r.so.5
#4  0x281b1d55 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5
#5  0x0 in ?? ()

#0  0x2819e184 in getegid () from /usr/lib/libc_r.so.5
#1  0x281eb61e in abort () from /usr/lib/libc_r.so.5
#2  0x281b6015 in _thread_exit () from /usr/lib/libc_r.so.5
#3  0x281af42e in _pq_init () from /usr/lib/libc_r.so.5
#4  0x281b1cd5 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5
#5  0x0 in ?? ()

/ Thomas Stromberg

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to