Super, thanks
On Wed, Oct 2, 2019 at 5:31 PM Ben Pfaff wrote:
> On Wed, Oct 02, 2019 at 11:37:52AM +0200, Damijan Skvarc wrote:
> > memory leaks are reported in several tests and are expressed in a
> following way:
> >
> > ==29840== 208 (48 direct, 160 indirect) bytes in 1 blocks are definitely
On Wed, Oct 02, 2019 at 11:37:52AM +0200, Damijan Skvarc wrote:
> memory leaks are reported in several tests and are expressed in a following
> way:
>
> ==29840== 208 (48 direct, 160 indirect) bytes in 1 blocks are definitely lost
> in
> loss record 43 of 44
> ==29840==at 0x4C2FB55: calloc
Thanks for informing me. I have resent new patch request.
regards,Damijan
On Tue, Oct 1, 2019 at 6:28 PM Ben Pfaff wrote:
> On Tue, Oct 01, 2019 at 09:22:29AM +0200, Damijan Skvarc wrote:
> > memory leaks are reported in several tests and are expressed in a
> following way:
> >
> > ==29840==
memory leaks are reported in several tests and are expressed in a following way:
==29840== 208 (48 direct, 160 indirect) bytes in 1 blocks are definitely lost in
loss record 43 of 44
==29840==at 0x4C2FB55: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64
-linux.so)
==29840==by
On Tue, Oct 01, 2019 at 09:22:29AM +0200, Damijan Skvarc wrote:
> memory leaks are reported in several tests and are expressed in a following
> way:
>
> ==29840== 208 (48 direct, 160 indirect) bytes in 1 blocks are definitely lost
> in loss record 43 of 44
> ==29840==at 0x4C2FB55: calloc
Bleep bloop. Greetings Damijan Skvarc, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
git-am:
fatal: sha1 information is lacking or useless (ovsdb/ovsdb-client.c).
Repository lacks necessary
memory leaks are reported in several tests and are expressed in a following way:
==29840== 208 (48 direct, 160 indirect) bytes in 1 blocks are definitely lost
in loss record 43 of 44
==29840==at 0x4C2FB55: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==29840==by
