5 ms·
http://www.cs.berkeley.edu/~necula/Papers/ccured_popl02.pdf http://www.cs.berkeley.edu/~necula/Papers/ccured_popl02.pdf https://en.wikipedia.org/wiki/Cyclone_%
by GregBuchholz 10y ago
http://www.cs.berkeley.edu/~necula/Papers/ccured_popl02.pdf http://www.cs.berkeley.edu/~necula/Papers/ccured_popl02.pdf
https://en.wikipedia.org/wiki/Cyclone_%28programming_language%29 https://en.wikipedia.org/wiki/Cyclone_%28programming_languag...
http://elinux.org/Electric_Fence http://elinux.org/Electric_Fence
http://valgrind.org/ http://valgrind.org/
https://github.com/google/sanitizers https://github.com/google/sanitizers
https://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis#C.2C_C.2B.2B https://en.wikipedia.org/wiki/List_of_tools_for_static_code_...
- krylon 10y agoThanks! I had used valgrind before on a toy project to find memory leaks, but I had not used any of the other tools it offers. I remember that back then it did not work terribly well for bounds checking, but that was years ago. 2009-ish. Electric Fence I have heard of before, but I never tried it. I will definitely come back to these links when I am working in C the next time.