pcp
[Top] [All Lists]

Re: [pcp] Patch for Python's pmExtractValue Function

To: Tom Yearke <tyearke@xxxxxxxxxxx>
Subject: Re: [pcp] Patch for Python's pmExtractValue Function
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 14 Apr 2014 04:22:11 -0400 (EDT)
Cc: Stan Cox <scox@xxxxxxxxxx>, pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <534B6428.1090709@xxxxxxxxxxx>
References: <53342449.7070602@xxxxxxxxxxx> <53446B81.4020602@xxxxxxxxxx> <235383721.4734118.1397439752269.JavaMail.zimbra@xxxxxxxxxx> <534B6428.1090709@xxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: UCpDh1hRz0EgEFWXJitOpbxecJfRQg==
Thread-topic: Patch for Python's pmExtractValue Function
Hi Tom,

----- Original Message -----
> Sorry about the delay in getting back to you all. I've had a number of
> other issues come up over the last few days that have prevented me from
> more fully investigating the issue, which I had hoped to do before
> replying but have not yet.

No problem at all - I believe Stan has strained his back and has been
offline a fair bit as well.

> I am hoping to finally get back to this issue in the morning, my
> timezone, but if you'd like to take a look in the meantime, I would
> welcome it. I'm afraid I don't have a script that's not tightly coupled
> to other resources to share, but calling pmExtractValue with a pmResult
> for a string metric, followed by losing the reference to the returned
> pmAtomValue, will create the leak. The example code at the top of
> pmapi.py should be a good starting point.

OK, thanks!  I've run out of time for today, but hope to look into
it more deeply tomorrow.

cheers.

--
Nathan

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