| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH 0 of 3] libxl: memory leaks
On 02/08/10 15:05, Gianni Tedesco (3P) wrote:
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...
What about, what's wrong with the original design ?
the original design being you stuff everything in the context memtrack
and expect all the objects allocated by libxl (internal AND returned to
the caller) to be free by a ctx_free. This provides a strong proven
guarantee that *everything* has been free.
--
Vincent
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home