Re: [Qemu-devel] port io mem leak

2012-02-29 Thread Avi Kivity
On 02/29/2012 06:39 PM, Michael S. Tsirkin wrote: > On Wed, Feb 29, 2012 at 06:36:10PM +0200, Avi Kivity wrote: > > On 02/29/2012 06:18 PM, Anthony Liguori wrote: > > > On 02/29/2012 10:16 AM, Michael S. Tsirkin wrote: > > >> Valgrind shows a memory leak below: > > > > > > Is this with Avi's latest

Re: [Qemu-devel] port io mem leak

2012-02-29 Thread Michael S. Tsirkin
On Wed, Feb 29, 2012 at 06:39:25PM +0200, Michael S. Tsirkin wrote: > On Wed, Feb 29, 2012 at 06:36:10PM +0200, Avi Kivity wrote: > > On 02/29/2012 06:18 PM, Anthony Liguori wrote: > > > On 02/29/2012 10:16 AM, Michael S. Tsirkin wrote: > > >> Valgrind shows a memory leak below: > > > > > > Is this

Re: [Qemu-devel] port io mem leak

2012-02-29 Thread Michael S. Tsirkin
On Wed, Feb 29, 2012 at 06:36:10PM +0200, Avi Kivity wrote: > On 02/29/2012 06:18 PM, Anthony Liguori wrote: > > On 02/29/2012 10:16 AM, Michael S. Tsirkin wrote: > >> Valgrind shows a memory leak below: > > > > Is this with Avi's latest branch or is this in qemu.git? > > Looks like qemu.git. Thi

Re: [Qemu-devel] port io mem leak

2012-02-29 Thread Avi Kivity
On 02/29/2012 06:18 PM, Anthony Liguori wrote: > On 02/29/2012 10:16 AM, Michael S. Tsirkin wrote: >> Valgrind shows a memory leak below: > > Is this with Avi's latest branch or is this in qemu.git? Looks like qemu.git. -- error compiling committee.c: too many arguments to function

Re: [Qemu-devel] port io mem leak

2012-02-29 Thread Michael S. Tsirkin
On Wed, Feb 29, 2012 at 10:18:23AM -0600, Anthony Liguori wrote: > On 02/29/2012 10:16 AM, Michael S. Tsirkin wrote: > >Valgrind shows a memory leak below: > > Is this with Avi's latest branch or is this in qemu.git? > > Regards, > > Anthony Liguori Avi's latest branch. > > > >==21745== 208 (1

Re: [Qemu-devel] port io mem leak

2012-02-29 Thread Anthony Liguori
On 02/29/2012 10:16 AM, Michael S. Tsirkin wrote: Valgrind shows a memory leak below: Is this with Avi's latest branch or is this in qemu.git? Regards, Anthony Liguori ==21745== 208 (112 direct, 96 indirect) bytes in 2 blocks are definitely lost in loss record 588 of 856 ==21745==at 0x

[Qemu-devel] port io mem leak

2012-02-29 Thread Michael S. Tsirkin
Valgrind shows a memory leak below: ==21745== 208 (112 direct, 96 indirect) bytes in 2 blocks are definitely lost in loss record 588 of 856 ==21745==at 0x4A05FDE: malloc (vg_replace_malloc.c:236) ==21745==by 0x24D4C5: malloc_and_trace (vl.c:2156) ==21745==by 0x50637D2: g_malloc (in /li