From: Thomas Huth <thuth@linux.vnet.ibm.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] coverity: Improve model for GLib memory allocation
Date: Fri, 23 Jan 2015 13:04:03 +0100 [thread overview]
Message-ID: <20150123130403.2037e11d@oc7435384737.ibm.com> (raw)
In-Reply-To: <873872sw4g.fsf@blackfin.pond.sub.org>
On Thu, 22 Jan 2015 15:55:27 +0100
Markus Armbruster <armbru@redhat.com> wrote:
...
>
> == Triaged / Bug ==
>
> These are worrying. Something wrong with my new model?
>
> hw/s390x/s390-pci-bus.c:195: leaked_storage: Variable "sei_cont" going out of scope leaks the storage it points to.
Did you already include the fix for the sei_count leak before you ran
the test?
(http://lists.nongnu.org/archive/html/qemu-devel/2015-01/msg02348.html)
Thomas
next prev parent reply other threads:[~2015-01-23 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 14:45 [Qemu-devel] [PATCH RFC] coverity: Improve model for GLib memory allocation Markus Armbruster
2015-01-22 14:55 ` Markus Armbruster
2015-01-22 15:53 ` Paolo Bonzini
2015-01-23 12:04 ` Markus Armbruster
2015-01-23 12:04 ` Thomas Huth [this message]
2015-01-28 14:49 ` Markus Armbruster
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=20150123130403.2037e11d@oc7435384737.ibm.com \
--to=thuth@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=pbonzini@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).