Writing large C projects without tools like valgrind is crazy! I guess in some situations it can be hard to set up (like kernel programming.) but user space sof

Writing large C projects without tools like valgrind is crazy! I guess in some situations it can be hard to set up (like kernel programming.) but user space software should always be written with it. My personal experience is tools like valgrind will immediately shove stupid mistakes back in your face (rather than waiting a few days to realize the change you made is corrupting the heap in a way that eventually causes the program to crash.) and the result is not only better memory management in your project but also better memory management in future projects.