From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 0 of 3] libxl: memory leaks
Date: Mon, 02 Aug 2010 13:31:10 +0100 [thread overview]
Message-ID: <patchbomb.1280752270@localhost.localdomain> (raw)
The following fix a few memory leaks.
The first was discussed on list and it was decided that although it
wasn't a real leak, since the memory is allocated exactly once per
thread and is correctly cleaned up on pthread_exit(), it was still
useful for xl (a non-threaded application) to be able to be completely
valgrind clean for the purposes of auditing libxl.
The leaks fixed in xl create are just a subset since I didn't delve
into recursively freeing the types defined by libxl yet. There are
also leaks in the lexer and parser which I didn't tackle yet.
next reply other threads:[~2010-08-02 12:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 12:31 Ian Campbell [this message]
2010-08-02 12:31 ` [PATCH 1 of 3] libxc: free thread specific hypercall buffer on xc_interface_close Ian Campbell
2010-08-02 12:31 ` [PATCH 2 of 3] libxl: fix memory leak in libxl_name_to_domid Ian Campbell
2010-08-02 12:31 ` [PATCH 3 of 3] xl: fix memory leaks in xl create Ian Campbell
2010-08-02 13:11 ` [PATCH 0 of 3] libxl: memory leaks Gianni Tedesco
2010-08-02 13:20 ` Vincent Hanquez
2010-08-02 14:05 ` Gianni Tedesco
2010-08-03 7:59 ` Vincent Hanquez
2010-08-03 10:18 ` Gianni Tedesco
2010-08-03 10:51 ` Vincent Hanquez
2010-08-03 12:16 ` Gianni Tedesco
2010-08-03 13:37 ` Vincent Hanquez
2010-08-03 14:02 ` Gianni Tedesco
2010-08-03 14:51 ` Ian Campbell
2010-08-03 17:07 ` Stefano Stabellini
2010-08-03 17:11 ` Stefano Stabellini
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=patchbomb.1280752270@localhost.localdomain \
--to=ian.campbell@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.