Richard Lyons napisał(a):
gcc-3.4 is known to generate incorrect code when optimising on x86_64 (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21804), it may be the cause of the segfault. If removing the optimisations doesn't help you might try gcc-4. Rick.
OK it wasn't caused by optimisations. I removed all flags and left only -march=nocona. It seems that thiis is a squid bug, bug on squids bugzilla they ask me to run malloc debuger which I can't do. I am afraid it is good time to go back to 32 bit :\.
-- Michał Margula, alchemyx@xxxxxxxxxxxx, http://alchemyx.uznam.net.pl/ "W życiu piękne są tylko chwile" [Ryszard Riedel]
