Determine how to handle coverity issues

[pki-bot]

This issue was migrated from Pagure Issue #35. Originally filed by vakwetu (@vakwetu) on 2011-11-15 07:20:59:

• Closed as Invalid
• Assigned to nkinder (@nkinder)

---

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

[pki-bot]

Comment from nkinder (@nkinder) at 2012-05-17 19:52:10

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

[pki-bot]

Comment from vakwetu (@vakwetu) at 2017-02-27 14:04:39

Metadata Update from @vakwetu:

• Issue assigned to nkinder
• Issue set to the milestone: Dogtag 10.0 - Phase 2