I had to disable this as it was impacting operations. I’ll try to
reproduce in test instance when I can. Mainly just wanted to see if
anyone has experienced it here. There are numerous other references
across the web to that perl regex issue, but I didn’t see any posts
here.
This issue may be with perl, but I’d be curious to see what regex are
triggering it…
http://groups.google.com/group/perl.perl5.porters/browse_thread/thread/94914fe2d844f5ec/2860ab39fbae7c9c?lnk=raot
Thanks,
Brian
perl-5.10.0-62.18.1 [SuSE 11.1]
Summary of my perl5 (revision 5 version 10 subversion 0) configuration:
Platform:
osname=linux, osvers=2.6.27, archname=x86_64-linux-thread-multi
uname=‘linux haley 2.6.27 #1 smp 2009-02-09 15:38:31 +0100 x86_64
x86_64 x86_64 gnulinux ’
config_args=’-ds -e -Dprefix=/usr -Dvendorprefix=/usr
-Dinstallusrbinperl -Dusethreads -Di_db -Di_dbm -Di_ndbm -Di_gdbm
-Duseshrplib=true -Doptimize=-fmessage-length=0 -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
-fasynchronous-unwind-tables -g -Wall -pipe
-Accflags=-DPERL_USE_SAFE_PUTENV’
hint=recommended, useposix=true, d_sigaction=define
useithreads=define, usemultiplicity=define
useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
use64bitint=define, use64bitall=define, uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc=‘cc’, ccflags =‘-D_REENTRANT -D_GNU_SOURCE
-DPERL_USE_SAFE_PUTENV -DDEBUGGING -fno-strict-aliasing -pipe
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64’,
optimize=‘-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2
-fstack-protector -funwind-tables -fasynchronous-unwind-tables -g
-Wall -pipe’,
cppflags=‘-D_REENTRANT -D_GNU_SOURCE -DPERL_USE_SAFE_PUTENV
-DDEBUGGING -fno-strict-aliasing -pipe’
ccversion=‘’, gccversion=‘4.3.2 [gcc-4_3-branch revision 141291]’,
gccosandvers=‘’
intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype=‘long’, ivsize=8, nvtype=‘double’, nvsize=8, Off_t=‘off_t’,
lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld=‘cc’, ldflags =’ -L/usr/local/lib64’
libpth=/lib64 /usr/lib64 /usr/local/lib64
libs=-lm -ldl -lcrypt -lpthread
perllibs=-lm -ldl -lcrypt -lpthread
libc=/lib64/libc-2.9.so, so=so, useshrplib=true, libperl=libperl.so
gnulibc_version=‘2.9’
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=‘-Wl,-E
-Wl,-rpath,/usr/lib/perl5/5.10.0/x86_64-linux-thread-multi/CORE’
cccdlflags=‘-fPIC’, lddlflags='-shared -L/usr/local/lib64’On Mon, Jan 11, 2010 at 12:24 PM, Kevin Falcone falcone@bestpractical.com wrote:
On Mon, Jan 11, 2010 at 11:22:46AM -0500, Brian D wrote:
Has anyone else experienced this issue with MakeClicky?
It appears to be triggering an internal perl assertion with Regular
Expressions, this doesn’t look like an easy one to troubleshoot…
In some cases it is preventing the display of the entire ticket, in
others it is only printing this message in the display at one point of
the output.
Wed Jan 06 11:22:37 2010 The RT System itself - Outgoing email
recorded [Show]
Assertion rx->sublen >= (s - rx->subbeg) + i failed: file “regcomp.c”,
line 5109 at /srv/www/htdocs/rt/Elements/MakeClicky line 162
It would be really useful to know your perl -V, you can find it on
Configuration → Tools → System Configuration under the Perl
Configuration header.
You may also want to try and trim the relevant transaction content
down to the smallest possible section to isolate the perl bug
-kevin
List info: The rt-devel Archives