Thanks for all your advice. I will pay close attention next time.
On Thu, Nov 2, 2017 at 2:14 PM, Ben Pfaff wrote:
> On Tue, Oct 31, 2017 at 10:52:08AM -0700, Yifeng Sun wrote:
> > Valgrind testcase 2339 (ovn -- ipam connectivity) reports the leak below:
> > 45 (32 direct, 13
On Tue, Oct 31, 2017 at 10:52:08AM -0700, Yifeng Sun wrote:
> Valgrind testcase 2339 (ovn -- ipam connectivity) reports the leak below:
> 45 (32 direct, 13 indirect) bytes in 1 blocks are definitely lost in loss
> record 65 of 83
> at 0x4C2DB8F: malloc (in
>
Valgrind testcase 2339 (ovn -- ipam connectivity) reports the leak below:
45 (32 direct, 13 indirect) bytes in 1 blocks are definitely lost in loss
record 65 of 83
at 0x4C2DB8F: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x4A6D64: xmalloc (util.c:120)
by