| To: | Dave Brolley <brolley@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] PCP Updates: Active Probing for __pmDiscoverServices() / pmfind |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 22 May 2014 19:52:41 -0400 (EDT) |
| Cc: | PCP Mailing List <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <537E50B4.1090905@xxxxxxxxxx> |
| References: | <5373D0D2.5090902@xxxxxxxxxx> <1264071097.9700484.1400487393003.JavaMail.zimbra@xxxxxxxxxx> <537E50B4.1090905@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | y3WmpbHP0ZAF/NWUVcMrsDU1NUyL9A== |
| Thread-topic: | PCP Updates: Active Probing for __pmDiscoverServices() / pmfind |
----- Original Message ----- > On 05/19/2014 04:16 AM, Nathan Scott wrote: > > [...] > > (this allocation ultimately seems to lead to one or two potential > > memory leaks down the track ... but perhaps I'm missing something > > subtle there) > No memory leak here -- as discussed in earlier comments. > > Thanks for the review! Let me know what you think about the items I've > left open. > Those explanations all seem fine to me - thanks for following up & lemme know once all tested and ready to merge - I guess the sooner the better, to dodge any more git-merge conflicts. :) If you can think of a way to test that subtle memory alloc/freeing is correct (perhaps a _run_valgrind test on pmfind?) that would be super-mega-awesome. cheers. -- Nathan |
| Previous by Date: | Re: PCP Updates: Active Probing for __pmDiscoverServices() / pmfind, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] PCP Updates: Active Probing for __pmDiscoverServices() / pmfind, Nathan Scott |
| Previous by Thread: | Re: [pcp] PCP Updates: Active Probing for __pmDiscoverServices() / pmfind, Dave Brolley |
| Next by Thread: | Re: [pcp] PCP Updates: Active Probing for __pmDiscoverServices() / pmfind, Dave Brolley |
| Indexes: | [Date] [Thread] [Top] [All Lists] |