| To: | Lukas Berk <lberk@xxxxxxxxxx> |
|---|---|
| Subject: | pmdapapi buglets from Coverity scan |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Tue, 10 Feb 2015 18:57:54 -0500 (EST) |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <266702076.2689468.1423612211793.JavaMail.zimbra@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | PQiZXVqMuD8O2E2wurxmnWnga7J1tw== |
| Thread-topic: | pmdapapi buglets from Coverity scan |
Hi Lukas,
Coverity is reporting a couple of issues in pmdapapi that I
could use some help with if you could? It's saying the sts
setting here is dead code...
/*
* This is where we'd see if a requested counter was
* "one too many". We must leave a note for the
* function to return an error, but must continue (so
* that reactivating other counters is still
* attempted).
*/
sts = PM_ERR_VALUE;
continue;
which at first glance does indeed seem to be the case (it'll
be overwritten on subsequent loop iterations by PAPI_add_event).
papi_store it then says has a loop control issue - apparently
it can only execute the "for (i = 0; i < result->numpmid; i++)"
loop once. I think this is because the switch always returns a
result for the first PMID, when we should really be continuing
on through all metrics being stored to.
cheers.
--
Nathan
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: interp3.c vs valgrind qa fallout, Nathan Scott |
|---|---|
| Next by Date: | Re: Reduce pmdaproc.sh runtime for pmdaInstall, Nathan Scott |
| Previous by Thread: | interp3.c vs valgrind qa fallout, Nathan Scott |
| Next by Thread: | Re: pmdapapi buglets from Coverity scan, Lukas Berk |
| Indexes: | [Date] [Thread] [Top] [All Lists] |