On 10 September 2016 at 21:26, Ben Pfaff wrote:
> On Fri, Sep 09, 2016 at 01:48:53PM -0700, Joe Stringer wrote:
>> Valgrind reports:
>>
>> ==18725== 32 bytes in 1 blocks are definitely lost in loss record 339 of 497
>> ==18725==at 0x4C29BBE: malloc (in
>> /usr/lib/valgrind/vgpreload_memcheck-a
On Fri, Sep 09, 2016 at 01:48:53PM -0700, Joe Stringer wrote:
> Valgrind reports:
>
> ==18725== 32 bytes in 1 blocks are definitely lost in loss record 339 of 497
> ==18725==at 0x4C29BBE: malloc (in
> /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==18725==by 0x450F1F: xmalloc (uti
> On Sep 9, 2016, at 4:48 PM, Joe Stringer wrote:
>
> Valgrind reports:
>
> ==18725== 32 bytes in 1 blocks are definitely lost in loss record 339 of 497
> ==18725==at 0x4C29BBE: malloc (in
> /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==18725==by 0x450F1F: xmalloc (util.c:112
Valgrind reports:
==18725== 32 bytes in 1 blocks are definitely lost in loss record 339 of 497
==18725==at 0x4C29BBE: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==18725==by 0x450F1F: xmalloc (util.c:112)
==18725==by 0x41748E: replication_add_local_db (replication.c