Liubov Dmitrieva c044cf14b0 Fix wrong copying processing for last bytes in x86-32 wcscpy
Wrong copy algorithm for last bytes, not thread safety.
In some particular cases it uses the destination
memory beyond the string end for
16-byte load, puts changes into that part that is relevant
to destination string and writes whole 16-byte chunk into memory.
I have a test case where the memory beyond the string end contains
malloc/free data, that appear corrupted in case free() updates
it in between the 16-byte read and 16-byte write.
2011-12-23 08:50:39 -05:00
..
2009-08-28 14:54:46 -07:00
2011-10-23 14:28:26 -04:00
2010-01-12 11:28:17 -08:00
2011-10-12 11:42:57 -04:00
2011-10-12 11:42:57 -04:00
2010-01-12 11:28:17 -08:00
2011-10-23 16:30:40 -04:00
2010-04-14 22:27:59 -07:00
2010-10-13 22:27:03 -04:00
2010-04-14 22:27:59 -07:00
2010-10-11 09:27:05 -04:00
2011-08-04 15:38:35 -04:00
2009-12-13 15:23:02 -08:00
2011-10-28 12:02:08 +02:00
2010-08-24 11:35:01 -07:00
2010-04-14 22:27:59 -07:00
2011-10-23 13:35:24 -04:00
2011-09-05 13:54:51 -04:00