pcp
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

interp3.c vs valgrind qa fallout

from [Nathan Scott] [Permanent Link][Original]
To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: interp3.c vs valgrind qa fallout
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 10 Feb 2015 06:11:04 -0500 (EST)
Cc: "pcp@xxxxxxxxxxx >> PCP" <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <717061209.2027585.1423566421833.JavaMail.zimbra@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: R/l+QZkqqRxSAtQKldln5DL+vtAlPg==
Thread-topic: interp3.c vs valgrind qa fallout 
Hi Ken,

I'm running your latest dev with pmdaproc.sh speedup ... seeing the
attached qa fail - just FYI.  I'm not seeing any likely libpcp cause
so I'm punting this change is behind it at this stage:

commit 641cefaa599a66e55e2faf741581483dc1091650
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date:   Tue Feb 10 12:17:34 2015 +1100

    qa/src/interp3.c: free() the *alloc()s from main
    
    Avoids confusing valgrind in some places, like vm25 (x86_64
    CentOS 5.5).

Lemme know if its not ringing a bell & I'll dig further.

cheers.

--
Nathan

Attachment: 394.out.bad
Description: Binary data

[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  ipv6 and qa/533 question, Ken McDonell
Next by Date:  Re: [pcp] ipv6 and qa/533 question, Nathan Scott
Previous by Thread:  ipv6 and qa/533 question, Ken McDonell
Next by Thread:  Re: interp3.c vs valgrind qa fallout, Ken McDonell
Indexes:  [Date] [Thread] [Top] [All Lists]