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

2014-03-18 Thread Michael S. Tsirkin
On Mon, Mar 17, 2014 at 10:53:25PM +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==at

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

2014-03-18 Thread Markus Armbruster
Marcel Apfelbaum writes: > On Mon, 2014-03-17 at 22:53 +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

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

2014-03-17 Thread Marcel Apfelbaum
On Mon, 2014-03-17 at 22:53 +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==at 0x4031A

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

2014-03-17 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 (