https://bugs.kde.org/show_bug.cgi?id=402833
Olly Betts <ojwbetts+...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ojwbetts+...@gmail.com
--- Comment #11 from Olly Betts <ojwbetts+...@gmail.com> ---
I recently started seeing the "Source and destination overlap in memcpy_chk"
from a call be memmove which was already reported as
https://bugs.kde.org/show_bug.cgi?id=453084 which has been marked as a
duplicate of this bug. It also seems to be the same problem reported here in
comment 4.
I found the following suppression works:
{
memmove overlapping source and destination
Memcheck:Overlap
fun:__memcpy_chk
fun:memmove
}
This suppression only matches when __memcpy_chk is called by memmove so it
should only suppress the incorrect errors. I'm posting it here in the hope it
will help others who hit this and find this bug while seeking a workaround
(like I did before trying to a suppression).
(FWIW I'm using the valgrind package version 1:3.20.0-2.1 on Debian unstable.)
--
You are receiving this mail because:
You are watching all bug changes.
