[libvirt] [PATCH] Resolve valgrind error

2013-04-29 Thread John Ferlan
As a result of commit id '19c345f2', 'make -C tests valgrind' has the following for qemuxml2argvtest: ==22482== 197 (80 direct, 117 indirect) bytes in 1 blocks are definitely lost in loss record 101 of 120 ==22482==at 0x4A06B6F: calloc (vg_replace_malloc.c:593) ==22482==by 0x4C6F301:

Re: [libvirt] [PATCH] Resolve valgrind error

2013-04-29 Thread Michal Privoznik
On 29.04.2013 14:35, John Ferlan wrote: As a result of commit id '19c345f2', 'make -C tests valgrind' has the following for qemuxml2argvtest: ==22482== 197 (80 direct, 117 indirect) bytes in 1 blocks are definitely lost in loss record 101 of 120 ==22482==at 0x4A06B6F: calloc

Re: [libvirt] [PATCH] Resolve valgrind error

2013-04-29 Thread John Ferlan
On 04/29/2013 08:45 AM, Michal Privoznik wrote: On 29.04.2013 14:35, John Ferlan wrote: As a result of commit id '19c345f2', 'make -C tests valgrind' has the following for qemuxml2argvtest: ==22482== 197 (80 direct, 117 indirect) bytes in 1 blocks are definitely lost in loss record 101 of

Re: [libvirt] [PATCH] Resolve valgrind error

2013-04-16 Thread John Ferlan
On 04/15/2013 12:49 PM, John Ferlan wrote: Commit id '1acfc171' resulted in the following valgrind failure: ==25317== 136 (24 direct, 112 indirect) bytes in 1 blocks are definitely lost in loss record 4 of 4 ==25317==at 0x4A06B6F: calloc (vg_replace_malloc.c:593) ==25317==by

[libvirt] [PATCH] Resolve valgrind error

2013-04-15 Thread John Ferlan
Commit id '1acfc171' resulted in the following valgrind failure: ==25317== 136 (24 direct, 112 indirect) bytes in 1 blocks are definitely lost in loss record 4 of 4 ==25317==at 0x4A06B6F: calloc (vg_replace_malloc.c:593) ==25317==by 0x4C6F851: virAlloc (viralloc.c:124) ==25317==by

Re: [libvirt] [PATCH] Resolve valgrind error

2013-04-15 Thread Eric Blake
On 04/15/2013 10:49 AM, John Ferlan wrote: Commit id '1acfc171' resulted in the following valgrind failure: ==25317== 136 (24 direct, 112 indirect) bytes in 1 blocks are definitely lost in loss record 4 of 4 ==25317==at 0x4A06B6F: calloc (vg_replace_malloc.c:593) ==25317==by

[libvirt] [PATCH] Resolve valgrind error

2013-03-06 Thread John Ferlan
Resolves the following valgrind error from qemuxml2argvtest: ==20393== 5 bytes in 1 blocks are definitely lost in loss record 2 of 60 ==20393==at 0x4A0883C: malloc (vg_replace_malloc.c:270) ==20393==by 0x38D690A167: __vasprintf_chk (in /usr/lib64/libc-2.16.so) ==20393==by 0x4CB0D97:

Re: [libvirt] [PATCH] Resolve valgrind error

2013-03-06 Thread Guannan Ren
On 03/06/2013 09:49 PM, John Ferlan wrote: Resolves the following valgrind error from qemuxml2argvtest: ==20393== 5 bytes in 1 blocks are definitely lost in loss record 2 of 60 ==20393==at 0x4A0883C: malloc (vg_replace_malloc.c:270) ==20393==by 0x38D690A167: __vasprintf_chk (in

Re: [libvirt] [PATCH] Resolve valgrind error

2013-03-06 Thread John Ferlan
On 03/06/2013 09:21 AM, Guannan Ren wrote: On 03/06/2013 09:49 PM, John Ferlan wrote: --- src/conf/domain_conf.c | 1 + 1 file changed, 1 insertion(+) ACK Guannan Pushed, thanks John -- libvir-list mailing list libvir-list@redhat.com