[FUGSPBR] Squid caindo!!!!

[Renato Machado]

Do FAQ do Squid


11.48 Segment Violation at startup or upon first request 
Some versions of GCC (notably 2.95.1 through 2.95.3) have bugs with compiler 
optimization. These GCC bugs may cause NULL pointer accesses in Squid, 
resulting in a ``FATAL: Received Segment Violation...dying'' message and a 
core dump. 

You can work around these GCC bugs by disabling compiler optimization. The 
best way to do that is start with a clean source tree and set the CC options 
specifically: 

% cd squid-x.y
% make distclean
% setenv CFLAGS='-g -Wall'
% ./configure ...

To check that you did it right, you can search for AC_CFLAGS in src/Makefile: 

% grep AC_CFLAGS src/Makefile
AC_CFLAGS       = -g -Wall

Now when you recompile, GCC won't try to optimize anything: 
% make
Making all in lib...
gcc -g -Wall -I../include -I../include -c rfc1123.c
...etc...

NOTE: some people worry that disabling compiler optimization will negatively 
impact Squid's performance. The impact should be negligible, unless your 
cache is really busy and already runs at a high CPU usage. For most people, 
the compiler optimization makes little or no difference at all. 


> 
> Na console o squid manda o seguinte sinal: 
> 
> Jun 5 01:18:22 pinheiro /kernel: pid 19896 (squid), uid 65534: 
> exited on signal 6
> Jun 5 01:18:22 pinheiro squid[18232]: Squid Parent: child process 
> 19896 exited due to signal 6
> Jun 5 01:18:25 pinheiro squid[18232]: Squid Parent: child process 
> 19929 started
> Jun 5 01:20:39 pinheiro /kernel: pid 19929 (squid), uid 65534: 
> exited on signal 6 
> 
> Eu ja recriei o /usr/local/squid/cache mas, nao adiantou. 
> 
> Alguem tem alguma dica do que pode estar acontecendo? 
> 
> ______________________________________________
> http://www2.fugspbr.org/mailman/listinfo/fugspbr
------- End of Original Message -------

______________________________________________
http://www2.fugspbr.org/mailman/listinfo/fugspbr