On Tue, 2011-03-22 at 17:11 +0100, Mark Martinec wrote:
> Matt,
>
> Thank you for troubleshooting. Well done!
Indeed! I am very glad to have slightly nudged Matt towards the dev
list, and him to quickly follow that advice -- after he already flooded
my Inbox with all his findings and progress. :)
Mark, how positive are you, that the Perl bug you filed is the real,
underlying issue? Seeing all these reports about effected systems, and
seemingly identical systems not effected...
Can we come up with some (brief) instructions, and a test rule that
should trigger the bug? So we can have those previously effected verify
it, and more importantly, verify the (tiny) patch to fix the issue for
them? A test case to be sure, whether or not future rule updates even
would include what's just broken the compile?
Also, while this Perl bug is out there (which undoubtful will exists for
a long time on production machines), should we refrain from tflags
multiple body rules?
Guess we cannot push them, unless guarded by a version 3.3.2 if-block.
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
