Bug 712381 - CoverityScan issues in kdelibs
Summary: CoverityScan issues in kdelibs
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kdelibs
Version: 7.0
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Grulich
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-10 13:05 UTC by Lukáš Tinkl
Modified: 2015-07-15 09:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-15 09:13:26 UTC
Target Upstream Version:


Attachments (Terms of Use)
Proposed patch against 4.6 branch (30.17 KB, patch)
2011-06-10 15:46 UTC, Lukáš Tinkl
no flags Details | Diff

Description Lukáš Tinkl 2011-06-10 13:05:10 UTC
Description of problem:
Coverity static analysis tool reported various issues in kdelibs source. Those
issues should be inspected.

Version-Release number of selected component (if applicable):
4.6.2-1


See https://dell-per610-03.lab.eng.brq.redhat.com/coverity/rhel-7-20110422/kdelibs-4.6.2-1.fc15/run1/

Comment 1 Lukáš Tinkl 2011-06-10 15:46:27 UTC
Created attachment 504151 [details]
Proposed patch against 4.6 branch

Comment 4 Ludek Smid 2014-06-26 10:41:41 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.

Comment 5 Ludek Smid 2014-06-26 11:16:32 UTC
The comment above is incorrect. The correct version is bellow.
I'm sorry for any inconvenience.
---------------------------------------------------------------

This request was NOT resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you need
to escalate this bug.

Comment 9 Jan Grulich 2015-07-15 09:13:26 UTC
I think we can close this one. I already fixed and reviewed all coverity scan issues in the latest version of kdelibs for RHEL 7.2 as a part of errata process.


Note You need to log in before you can comment on or make changes to this bug.