RE: [squid-users] squid 2.7 ... memory leak?

Care to explain how do you able to figure out in that instant?
Anyway after remove ubuntu's libcap2-dev ... leaks gone.

> -----Original Message-----
> From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
> Sent: Wednesday, October 12, 2011 5:59 AM
> To: squid-users_at_squid-cache.org
> Subject: Re: [squid-users] squid 2.7 ... memory leak?
>
> On Wed, 12 Oct 2011 01:32:00 +0800, jiluspo wrote:
> > (valgrind --tool=memcheck --leak-check=yes squid -Nd1)
> > 2011/10/12 01:25:38| Asking valgrind for memleaks
> > ==9877== 36 bytes in 1 blocks are definitely lost in loss record 606
> > of
> > 1,292
> > ==9877== at 0x4026864: malloc (vg_replace_malloc.c:236)
> > ==9877== by 0x407BFD5: cap_init (in /lib/libcap.so.2.20)
> > ==9877== by 0x407C0FB: cap_get_proc (in /lib/libcap.so.2.20)
> > ==9877== by 0x80C651B: restoreCapabilities (tools.c:1367)
> > ==9877== by 0x80C72FA: leave_suid (tools.c:644)
> > ==9877== by 0x809DB9F: setEffectiveUser (main.c:500)
> > ==9877== by 0x809E835: main (main.c:549)
> > ==9877==
> <snip>
> > does anybody care to explain why 36 bytes appeared?
>
> This is a leak in your /lib/libcap.so.2.20 library.
>
> Amos
>
> Email secured by Check Point

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.