Skip to main content

Browse the archive

Staging
v0.5.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision 296383b6d05f9617283aeb5b601106f84b016198 authored by Miss Islington (bot) on 19 January 2020, 22:44:04 UTC, committed by GitHub on 19 January 2020, 22:44:04 UTC 
bpo-35561: Supress valgrind false alarm on epoll_ctl(event) (GH-18060)
 

Update Misc/valgrind-python.supp to suppress the false alarm.
(cherry picked from commit d8ef64422a75f40cecdb1a7ee43492607d3daaf6)

Co-authored-by: Zackery Spytz <zspytz@gmail.com>
1 parent d96b7dd
Raw File
Tip revision: 296383b6d05f9617283aeb5b601106f84b016198 authored by Miss Islington (bot) on 19 January 2020, 22:44:04 UTC
bpo-35561: Supress valgrind false alarm on epoll_ctl(event) (GH-18060)
Tip revision: 296383b
README.coverity 

Coverity has a static analysis tool (Prevent) which is similar to Klocwork.
They run their tool on the Python source code (SVN head) on a daily basis.
The results are available at:

     http://scan.coverity.com/

About 20 people have access to the analysis reports.  Other
people can be added by request.

Prevent was first run on the Python 2.5 source code in March 2006.
There were originally about 100 defects reported.  Some of these
were false positives.  Over 70 issues were uncovered.

Each warning has a unique id and comments that can be made on it.
When checking in changes due to a warning, the unique id
as reported by the tool was added to the SVN commit message.

False positives were annotated so that the comments can
be reviewed and reversed if the analysis was incorrect.

Contact python-dev@python.org for more information.
back to top