3 ms·
Dunno what he does now, but he worked quite a bit in static analysis, which does a much better job at discovering nasty code properties than tests do. He found
by brohee 6y ago
Dunno what he does now, but he worked quite a bit in static analysis, which does a much better job at discovering nasty code properties than tests do.
He found issues in code you most likely rely on, like the Linux kernel : https://linux.kernel.narkive.com/Cw4EtIti/coverity-untrusted-user-data-in-kernel https://linux.kernel.narkive.com/Cw4EtIti/coverity-untrusted..., and also the pretty important CVE-2010-5298 in OpenSSL.
- UncleEntity 6y ago> I was under the impression that kmalloc has an implicit bounds check as it returns null if attempting to allocate >64kb (or at least it used to). Can someone confirm/disconfirm that? If only it had a unit test...