From: "tang.junhui"
Memroy API use mem_allocated to record the total size of used memory,
however, it's wrong to use size(p) as the length of freed memory in xfree(),
and memory may also be allocated by STRDUP() or REALLOC(), which is
not calculated into mem_allocated, so the total size of used m
On 08/15/16 03:59, tang.jun...@zte.com.cn wrote:
> From: "tang.junhui"
>
> Memroy API use mem_allocated to record the total size of used memory,
> however, it's wrong to use size(p) as the length of freed memory in xfree(),
> and memory may also be allocated by STRDUP() or REALLOC(), which is
> no
On Mon, Aug 15, 2016 at 06:59:09PM +0800, tang.jun...@zte.com.cn wrote:
> From: "tang.junhui"
>
> Memroy API use mem_allocated to record the total size of used memory,
> however, it's wrong to use size(p) as the length of freed memory in xfree(),
> and memory may also be allocated by STRDUP() or
On 08/15/16 05:11, Xose Vazquez Perez wrote:
> libmultipath/memory.[ch] files along with libmultipath/parser.[ch] and
> libmultipath/vector.[ch] come from keepalived/lib/ [1] .
>
> Maybe it's worth to backport their fixes and new features.
Hello Xose,
Are you aware that there are tools available
tang.junhui wrote:
> Memroy API use mem_allocated to record the total size of used memory,
> however, it's wrong to use size(p) as the length of freed memory in xfree(),
> and memory may also be allocated by STRDUP() or REALLOC(), which is
> not calculated into mem_allocated, so the total size of
From: "tang.junhui"
Memroy API use mem_allocated to record the total size of used memory,
however, it's wrong to use size(p) as the length of freed memory in xfree(),
and memory may also be allocated by STRDUP() or REALLOC(), which is
not calculated into mem_allocated, so the total size of used m
