[gs-bugs] [Bug 691395] Audit all calls to memcpy(), or replace with memmove()?

[bugzilla-daemon at ghostscript.com]

http://bugs.ghostscript.com/show_bug.cgi?id=691395

Alex Cherepanov <alex.cherepanov at artifex.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |alex.cherepanov at artifex.com
         Resolution|                            |WORKSFORME

--- Comment #1 from Alex Cherepanov <alex.cherepanov at artifex.com> 2010-06-14 19:08:58 UTC ---
(1) is a fine plan but proving anything about a program is rather
difficult. memcpy() is already used where the overlap is not expected.
I's difficult to imagine an implementation where memcpy(p,p,sizeof(*p))
will spoil *p . At least, libc on Linux and Windows works just file
in this case. Valgrind easily finds these bugs and all of them
have been fixed by the rev. 11374.

(2) Changing all memcpy() to memmove() will decrease the performance
and hide unexpected overlaps from Valgrind.

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.