Posted Nov 11, 2010 2:06 UTC (Thu) by gmaxwell (subscriber, #30048)
Parent article: Glibc change exposing bugs
I've run quite a bit of code through valgrind— and I don't believe I've ever actually seen the overlapping memcpy error. Even though it seems like an easy mistake it would seem that (almost) no one actually makes it.
That the error was found in flash, of all places, is not surprising. It's also scary that no one at adobe has been running flash in valgrind (but also not surprising).