Re: [Spice-devel] [PATCH spice-server] ci: Workaround bug in Valgrind detecting memcpy instead of memmove

2018-04-17 Thread Christophe Fergeau
On Mon, Apr 16, 2018 at 02:07:57PM -0400, Frediano Ziglio wrote: > > > > On Mon, Apr 16, 2018 at 05:02:33PM +0100, Frediano Ziglio wrote: > > > Due to a bug in current packaged Valgrind check-valgrind is failing > > > with: > > > > > > ==17986== Source and destination overlap in memcpy_chk(0x72c0

Re: [Spice-devel] [PATCH spice-server] ci: Workaround bug in Valgrind detecting memcpy instead of memmove

2018-04-16 Thread Frediano Ziglio
> > On Mon, Apr 16, 2018 at 05:02:33PM +0100, Frediano Ziglio wrote: > > Due to a bug in current packaged Valgrind check-valgrind is failing > > with: > > > > ==17986== Source and destination overlap in memcpy_chk(0x72c060, 0x72c068, > > 33) > > ==17986==at 0x4C344F0: __memcpy_chk (vg_replace

Re: [Spice-devel] [PATCH spice-server] ci: Workaround bug in Valgrind detecting memcpy instead of memmove

2018-04-16 Thread Christophe Fergeau
On Mon, Apr 16, 2018 at 05:02:33PM +0100, Frediano Ziglio wrote: > Due to a bug in current packaged Valgrind check-valgrind is failing > with: > > ==17986== Source and destination overlap in memcpy_chk(0x72c060, 0x72c068, 33) > ==17986==at 0x4C344F0: __memcpy_chk (vg_replace_strmem.c:1581) > =

[Spice-devel] [PATCH spice-server] ci: Workaround bug in Valgrind detecting memcpy instead of memmove

2018-04-16 Thread Frediano Ziglio
Due to a bug in current packaged Valgrind check-valgrind is failing with: ==17986== Source and destination overlap in memcpy_chk(0x72c060, 0x72c068, 33) ==17986==at 0x4C344F0: __memcpy_chk (vg_replace_strmem.c:1581) ==17986==by 0x40E7E9: check_vmc_error_message (test-stream-device.c:166) =