Search squid archive

Re: Squid 3.0 Segmentation Fault with ESI

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



fre 2009-02-13 klockan 08:16 +0000 skrev Duncan Booth:
> I'm trying to use Squid 3 with ESI enabled, and while it works fine for 
> a few pages as soon as we put it under load it just crashes. I've tried 
> a variety of squid 3.0 versions: from STABLE6 (which is the one we used 
> on our development system) up to 3.0.STABLE13-20090212 and they all 
> behave the same.

Quite expected. There hasn't been any changes in ESI.

> and the stacktrace below is from this version of squid:
> Squid Cache: Version 3.0.STABLE6

File a bug report please.

http://bugs.squid-cache.org/

> (gdb) where
> #0  0x0806d68c in ~cbdata (this=0xb7cfc128) at cbdata.cc:219
> #1  0x0806d991 in cbdataInternalFree(void*) (p=0x21) at cbdata.cc:376
> #2  0x080a676a in ESISegment::operator delete(void*) 
> (address=0xc7aaef31) at ESISegment.cc:166

Probably a double delete of the same object.

Try running squid under valgrind (with valgrind support compiled in).
May provide earlier or more exact hints to what goes wrong.

Regards
Henrik


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux