#35 Determine how to handle coverity issues
Closed: Invalid None Opened 12 years ago by vakwetu.

Coverity reports the following:

  • 89 resource leaks -- mostly not closing data streams in finally blocks etc. These should all be handled consistently
  • 10 class hierarchy violation
  • 42 concurrency violation
  • 1 control flow (unreachable code)
  • 2 incorrect expression
  • 1 integer handling
  • 266 null pointer derefs
  • 123 findbugs: bad practice
  • 599 findbugs : dodgy
  • 238 findbugs: performance
  • 21 findbugs: correctness
  • 14 findbugs: multithreaded correctness

We need to figure out how to create bugs/tasks accordingly


This will be handled as separate tickets for different classes of Coverity issues. Closing this ticket.

Metadata Update from @vakwetu:
- Issue assigned to nkinder
- Issue set to the milestone: Dogtag 10.0 - Phase 2

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/607

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata