Re: [patch] fixed overlapping memcpy() in if_xcmdsrv.c

2008/11/9 Matt Wozniski [EMAIL PROTECTED]: On Sat, Nov 8, 2008 at 11:18 PM, Tony Mechelynck wrote: Configure is supposed to check whether one of the system provided string-move operations handle overlap. Here's what I see in the logs and files produced by configure on my system: snip So

Re: [patch] fixed overlapping memcpy() in if_xcmdsrv.c

2008/11/9 Dominique Pelle [EMAIL PROTECTED]: $ gcc -Wall -o test-memcpy-memmove test-memcpy-memmove.c $ ./memcpy-memmove testing descending memcpy() with overlapping mem...OK testing ascending memcpy() with overlapping mem...FAIL expected=[abcdeabcdeabcdepqrstuvwxyz] actual

Re: [patch] fixed overlapping memcpy() in if_xcmdsrv.c

On 08/11/08 14:24, Bram Moolenaar wrote: Dominique Pelle wrote: While using Vim-7.2.30 built with GUI GTK (huge), I stumbled upon this error with Valgrind memory checker: ==13326== Source and destination overlap in memcpy(0x4B5D8D8, 0x4B5D8E4, 13) ==13326==at 0x4024C92: memcpy

Re: [patch] fixed overlapping memcpy() in if_xcmdsrv.c

On Sat, Nov 8, 2008 at 11:18 PM, Tony Mechelynck wrote: Configure is supposed to check whether one of the system provided string-move operations handle overlap. Here's what I see in the logs and files produced by configure on my system: snip So I suppose mch_memmove should be used