[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 887883] Re: Coverity scan revealed defects

From: Thomas Huth
Subject: [Qemu-devel] [Bug 887883] Re: Coverity scan revealed defects
Date: Sun, 08 Jan 2017 08:54:52 -0000

AFAIK a lot of issues reported by coverity have been addressed in the
recent versions of QEMU ... is there still anything left here that needs
special attention?

** Changed in: qemu
       Status: New => Incomplete

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  Coverity scan revealed defects

Status in QEMU:

Bug description:
  Coverity scan detected some issues such as  RESOURCE_LEAK and
  REVERSE_INULL etc on qemu-1.0rc1:

  Analysis summary report:
  Files analyzed                 : 830
  Total LoC input to cov-analyze : 576549
  Functions analyzed             : 20721
  Paths analyzed                 : 858376
  New defects found              : 428 Total
                                     2 ARRAY_VS_SINGLETON
                                     9 CHECKED_RETURN
                                    19 CONSTANT_EXPRESSION_RESULT
                                    60 DEADCODE
                                    43 FORWARD_NULL
                                    14 INFINITE_LOOP
                                    36 MISSING_BREAK
                                     3 MISSING_LOCK
                                    47 NEGATIVE_RETURNS
                                     1 NO_EFFECT
                                    11 NULL_RETURNS
                                    51 OVERRUN_STATIC
                                     1 RESOURCE_LEAK
                                    79 REVERSE_INULL
                                    20 SIGN_EXTENSION
                                     7 SIZEOF_MISMATCH
                                    15 UNINIT
                                     5 UNREACHABLE
                                     2 UNUSED_VALUE
                                     3 USE_AFTER_FREE

  For details, please see attachment.

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]