3 ms·
We had bounds checking GCC twenty five years ago. https://stuff.mit.edu/afs/sipb/project/bounds/src/gcc-2.7.2/bounds/report/bounds-checking.html https://stuff.
by kazinator 4y ago
We had bounds checking GCC twenty five years ago.
https://stuff.mit.edu/afs/sipb/project/bounds/src/gcc-2.7.2/bounds/report/bounds-checking.html https://stuff.mit.edu/afs/sipb/project/bounds/src/gcc-2.7.2/...
I played with that; it worked.
In the 90's I reached for Bruce Perens' Electric Fence; that did a good job for me.
We've Valgrind for some two decades now?
Call me unexcited ...
- pjmlp 4y agoAnd we have lint since 1979. What we miss is people actually using these tools in any meaningful way. Instead we have to go for hardware memory tagging and sandboxing, because there is no advocacy that changes their ways.
- rwmj 4y agoTo be fair the overhead of bounds checking GCC was rather large. Valgrind is a better and there's no excuse for not using it in your test suite. I doubt valgrind could realistically be used in production. -D_FORTIFY_SOURCE (=2) is used in production everywhere, assuming you're running some Red Hat or SUSE derived distro.