pcp
[Top] [All Lists]

Re: pcp updates: coverity, qa, martins+fche merges

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>, Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: pcp updates: coverity, qa, martins+fche merges
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 12 Feb 2015 19:59:39 -0500 (EST)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <y0msiea7jju.fsf@xxxxxxxx>
References: <2011032309.4022727.1423715962317.JavaMail.zimbra@xxxxxxxxxx> <54DC3C6D.4090005@xxxxxxxxxxxxxxxx> <900480755.4067256.1423720054914.JavaMail.zimbra@xxxxxxxxxx> <y0msiea7jju.fsf@xxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: sFC70dPAKf20CovtHa7zXZDi1B4Ikw==
Thread-topic: pcp updates: coverity, qa, martins+fche merges

----- Original Message -----
> > [...]
> >> 720 - valgrind detected errors
> >>   Command: pminfo -h
> >>   pcp://localhost?user=NOsuchUSER&pass=DEFINITELYnotApassword
> >> + 39 bytes in 1 blocks are definitely lost in loss record 14 of 38
> >> + at 0x4C2A1D4: calloc (in
> >> /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
> >> + by 0x4E86ADB: __pmAuthSecretCB (secureconnect.c:750)
> >> + by 0x5C2459A: _plug_get_password (in /usr/lib64/libsasl2.so.3.0.0)
> >> [...]
> > Not seeing that here; its a new test - looks like possibly a genuine
> > failure though & a bug still remaining in libpcp/sasl code?  commit
> > 2ae6cd0a4ce may have exposed this reporting?  Not sure, needs to be
> > investigated some more I think.
> 
> See the text for the pcp commit; this was already analyzed and
> reported to cyrus-sasl as a memory leak (RHBZ1191183).
> 

OK, sounds like the valgrind-suppress file needs to be further tweaked?

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>