Changes between Version 2 and Version 3 of GCI/Coding/CoverityIssues


Ignore:
Timestamp:
Sep 12, 2018, 7:19:16 PM (10 months ago)
Author:
Gedare Bloom
Comment:

Add directions for mentors, and clarify directions for students.

Legend:

Unmodified
Added
Removed
Modified
  • GCI/Coding/CoverityIssues

    v2 v3  
    33[[TOC(GCI/Coding/CoverityIssues , depth=2)]]
    44
     5Coverity Scan is a static analyzer that can identify various types of potential software defects. Coverity offers free use of this analyzer for free software projects. Issues identified for RTEMS are at https://scan.coverity.com/projects/rtems.
    56
    6 == Overview ==
     7Coverity Scan identifies POTENTIAL issues. Some may be real bugs. Others may indicate that Coverity Scan does not have full awareness of the program life. For example, memory allocated during RTEMS initialization may appear to be leaked because it is never freed, but this is deliberate and the issue marked as such in Coverity Scan.
    78
    8 Coverity Scan is a static analyzer that can identify various types of potential software defects. Coverity offers free use of this analyzer for free software projects. Issues identified for RTEMS at at https://scan.coverity.com/projects/rtems.
     9== Directions for Students ==
    910
    10 Coverity Scan identifies POTENTIAL issues. Some may be real bugs. Others may indicate that Coverity Scan does not have full awareness of the program life. For example, memory allocated during RTEMS initialization may appear to be leaked because it is never freed. But this deliberate and the issue marked as such in Coverity Scan.
     11For the purposes of Google Code-In, you will need to get an account on Coverity Scan and request access to the RTEMS Project. Then find an issue which is not included in the list of tickets below. Investigate the issue, and if it is a real bug then file a ticket at https://devel.rtems.org against 5.1 using ticket #3514 as a guide.
    1112
    12 For the purposes of Google Code-In, you will need to get an account on Coverity Scan and request access to the RTEMS Project. Then find an issue which is not included in the list of tickets below. File a ticket at https://devel.rtems.org against 5.1 using ticket #3514 as a guide.
    13 
    14 * The title should have an English summary and (CID number).
     13* The title should have an English summary and the CID number from the Coverity report.
    1514
    1615* The summary should include the offending code with some context.
     
    1817* If you can provide any insight into the issue, please feel free to add it. If the RTEMS source code has a copyright that indicates it originated in another project, please do make note of that. It is sometimes possible just to check the original source to see if the issue is fixed.
    1918
    20 == Tickets ==
     19* You may need to ask questions (on the devel mailing list or IRC) to confirm whether or not the Coverity issue is a real bug or not.
     20
     21=== Tickets ===
    2122
    2223The following open tickets correspond to Coverity issues.
    2324
    2425[[TicketQuery(status!=closed, keywords~=coverity, format=table, col=summary|owner, order=priority|id)]]
     26
     27== Directions for Mentors ==
     28
     29Compare the [https://scan.coverity.com/projects/rtems Coverity] report with the ticket that was filed. You'll need a Coverity account. Confirm the ticket appears in the table above, that the ticket contains the CID number and reproduces the problem/context of the Coverity report.
     30