https://bugs.kde.org/show_bug.cgi?id=402833
--- Comment #12 from Paul Floyd <pjfl...@wanadoo.fr> --- Adding a suppression is probably not the answer. Running under memcheck there shouldn't even be a call to __memcpy_chk from memmove. The question is why Valgrind isn't rediecting the call to memmove? On Linux the memmove may have been replaced by a call to memcpy if the compiler deems it safe to do so. That does cause us problems as our checks are more conservative. What exactly is the error message? -- You are receiving this mail because: You are watching all bug changes.
