[squid-users] Why 'Segment Violation' still happens?

hi, all..

My Squid 2.4STABLE7 runs into a "FATAL: Segment Violation" error after
runing about 2 hours.
I've checked FAQ and confirmed it's not a gcc optimization problem.
Then what should it be?

----------------------------------------------------------------------------
(gdb) where
#0 0x281637b4 in kill () from /usr/lib/libc.so.4
#1 0x281a3b26 in abort () from /usr/lib/libc.so.4
#2 0x80a649c in death (sig=11) at tools.c:299 <--- Signal Segment Violation
#3 0xbfbfffac in ?? ()
#4 0x805f6a4 in clientSendMoreData (data=0x8fc5c00, buf=0x9a01000 "", size=-1)
    at client_side.c:1717
#5 0x80a1115 in storeClientCallback (sc=0x92578c0, sz=-1) at store_client.c:165
#6 0x80a2149 in storeUnregister (sc=0x92578c0, e=0xac412c0, data=0x8fc5c00)
    at store_client.c:528
#7 0x805cfd1 in httpRequestFree (data=0x8fc5c00) at client_side.c:768
#8 0x805d21e in connStateFree (fd=195, data=0x9672600) at client_side.c:808
#9 0x8064a7f in commCallCloseHandlers (fd=195) at comm.c:535
#10 0x8064c16 in comm_close (fd=195) at comm.c:592
#11 0x80934ac in pumpClose (data=0x9292400) at pump.c:321
#12 0x8093114 in pumpReadFromClient (fd=195, data=0x9292400) at pump.c:258
#13 0x806672f in comm_poll (msec=379) at comm_select.c:432
#14 0x8088f2d in main (argc=2, argv=0xbfbffc40) at main.c:738
#15 0x804a3d9 in _start ()
----------------------------------------------------------------------------------

Level#3 is quite odd. In Level#4,
clientSendMoreData called clientWriteComplete(fd, NULL, 0, COMM_OK, http);
However, why did the function pointer become 0xbfbfffac ?

(My platform is FreeBSD 4.6, gcc 2.95.3)

Ko Tensei
Kanazawa Institute of Technology, Japan.
Received on Fri Oct 04 2002 - 05:38:07 MDT