| To: | Mark Goodwin <mgoodwin@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] coding issues and defects uncovered by Coverity scans |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Thu, 02 Feb 2012 07:11:39 +1100 |
| Cc: | pcp <pcp@xxxxxxxxxxx> |
| In-reply-to: | <4F0E6C1B.1030005@xxxxxxxxxx> |
| References: | <4F0E6C1B.1030005@xxxxxxxxxx> |
On Thu, 2012-01-12 at 16:14 +1100, Mark Goodwin wrote: > Coverity is a sophisticated static code analysis tool. > Among other things, it checks for the conditions listed here: > https://www.securecoding.cert.org/confluence/display/seccode/Coverity+Prevent > > Below is the result of running a scan over the pcp src tree: > http://people.redhat.com/mgoodwin/pcp-cov/index.html I have another Coverity related question ... what is one expected to do with issues like this one? 40 FORWARD_NULL /src2/git/pcp/src/pmlogger/<stdout> yy_get_next_buffer UNINSPECTED I assume this is found in the bison output file, but there is no context or line number to help isolate the "issue". |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | oss.sgi.com mailing list memberships reminder, mailman-owner |
|---|---|
| Next by Date: | pcp updates, Nathan Scott |
| Previous by Thread: | oss.sgi.com mailing list memberships reminder, mailman-owner |
| Next by Thread: | Re: [pcp] coding issues and defects uncovered by Coverity scans, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |