| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks
On Mon, 2010-08-02 at 14:20 +0100, Vincent Hanquez wrote:
> On 02/08/10 14:11, Gianni Tedesco wrote:
> > These patches are all good news. You should be aware (if not already)
> > that we have a plan for dealing with the majority of remaining leaks, I
> > was going to implement it after my current PCI work. So if you are going
> > to go all the way with this we should talk... :)
> >
> what's this plan ?
It's no big secret or mystery - I only mentioned it because I had
planned to start work on it quite soon :)
Basically it is to implement properly the current pointer tracking code
in libxl such that allocations via libxl_(sprintf|malloc) and so on are
automatically free'd when returning out of the library to a caller.
Objects returned to callers will still be expected to be free()'d...
Of course, this doesn't address xl tool itself, so fixes there shouldn't
clash or duplicate effort.
Gianni
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home