| |||||||||||||
Why use such misleading names for functions?Why use such misleading names for functions?Posted Nov 25, 2010 10:52 UTC (Thu) by xav (guest, #18536)In reply to: Why use such misleading names for functions? by rvfh Parent article: On breaking things
> Last but not least, if memcpy() had always _really_ been unsafe, we would not have the problem today,as Adobe would have spotted and corrected the bug during development.
Just one Valgrind run found the problem. So the big lesson here is that Adobe doesn't even run Valgrind or equivalent (e.g. Purify) on their code. They wouldn't have corrected the bug during development, even if memcpy() had done a printf() to warn them.
No wonder their software is full of security holes.
(Log in to post comments)
|
|||||||||||||