Re: [Qemu-devel] [PATCHv2] vl.c: Fix memory leak in qemu_register_machine

2014-03-19 Thread Andreas Färber
Am 19.03.2014 14:21, schrieb Michael S. Tsirkin: > On Wed, Mar 19, 2014 at 12:24:27PM +0100, Christian Borntraeger wrote: >> since commit 261747f176f6 (vl: Use MachineClass instead of global >> QEMUMachine list) valgrind complains about the following: >> >> ==54082== 57 bytes in 3 blocks are defini

Re: [Qemu-devel] [PATCHv2] vl.c: Fix memory leak in qemu_register_machine

2014-03-19 Thread Michael S. Tsirkin
On Wed, Mar 19, 2014 at 12:24:27PM +0100, Christian Borntraeger wrote: > since commit 261747f176f6 (vl: Use MachineClass instead of global > QEMUMachine list) valgrind complains about the following: > > ==54082== 57 bytes in 3 blocks are definitely lost in loss record 365 of > 729 > ==54082==a

Re: [Qemu-devel] [PATCHv2] vl.c: Fix memory leak in qemu_register_machine

2014-03-19 Thread Andreas Färber
Am 19.03.2014 12:24, schrieb Christian Borntraeger: > since commit 261747f176f6 (vl: Use MachineClass instead of global > QEMUMachine list) valgrind complains about the following: > > ==54082== 57 bytes in 3 blocks are definitely lost in loss record 365 of > 729 > ==54082==at 0x4031AFE: malloc

[Qemu-devel] [PATCHv2] vl.c: Fix memory leak in qemu_register_machine

2014-03-19 Thread Christian Borntraeger
since commit 261747f176f6 (vl: Use MachineClass instead of global QEMUMachine list) valgrind complains about the following: ==54082== 57 bytes in 3 blocks are definitely lost in loss record 365 of 729 ==54082==at 0x4031AFE: malloc (vg_replace_malloc.c:292) ==54082==by 0x4145569: g_malloc (