qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Jia <ajia@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Bug 887883 <887883@bugs.launchpad.net>
Subject: Re: [Qemu-devel] [Bug 887883] Re: Coverity scan revealed defects
Date: Wed, 23 Nov 2011 03:43:04 -0500 (EST)	[thread overview]
Message-ID: <d22faf10-00ae-4142-a6df-d77459d0aa3c@zmail15.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <m34nxvl1jl.fsf@blackfin.pond.sub.org>

Markus, I think it will silence Coverity complain, 
that sounds good to me, thanks.

Regards,
Alex

----- Original Message -----
From: "Markus Armbruster" <armbru@redhat.com>
To: "Bug 887883" <887883@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Sent: Wednesday, November 23, 2011 3:51:10 PM
Subject: Re: [Qemu-devel] [Bug 887883] Re: Coverity scan revealed defects

Alex Jia <887883@bugs.launchpad.net> writes:

> This is latest result on qemu-1.0-rc3, and I notice that 'RESOURCE_LEAK'
> is 10 now:

RESOURCE_LEAK is crippled right now, because Coverity knows nothing
about glib.  I started teaching it, and I intend to share when ready.

  reply	other threads:[~2011-11-23  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09  5:31 [Qemu-devel] [Bug 887883] [NEW] Coverity scan revealed defects Alex Jia
2011-11-09  5:31 ` [Qemu-devel] [Bug 887883] " Alex Jia
2011-11-23  3:28 ` Alex Jia
2011-11-23  7:51   ` Markus Armbruster
2011-11-23  8:43     ` Alex Jia [this message]
2011-11-23 12:10       ` Markus Armbruster
2011-11-23  3:34 ` Alex Jia
2011-12-30 23:59 ` Dr. David Alan Gilbert
2017-01-08  8:54 ` Thomas Huth
2017-03-10  4:17 ` Launchpad Bug Tracker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d22faf10-00ae-4142-a6df-d77459d0aa3c@zmail15.collab.prod.int.phx2.redhat.com \
    --to=ajia@redhat.com \
    --cc=887883@bugs.launchpad.net \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).