On Sun, 2010-02-14 at 09:45 -0500, Michael Scheidell wrote:
> only does this on ONE system. all have similar setups, same ram, same
> cpu, same rev or re2c, same os.
> so out of hundreds of systems, why does this one die? why with sa 330
> and not sa 325?
> (yes, its a sares rule, yes, we don't need them anymore), but sa-compile
> is seeing something that is creating code that is segfaulting when
> compiling.
> and in fact, it either segv's in the compiler, and os catches it, or,
> every now and then, crashes the os and causes it to reboot.
Bad RAM?
--
char *t="\10pse\0r\0dtu...@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; }}}
