3 ms·
You need to be routinely running valgrind on every bit of C code you write, and that will catch uninitialized reads along with many other classes of bugs.
by rwmj 6y ago
You need to be routinely running valgrind on every bit of C code you write, and that will catch uninitialized reads along with many other classes of bugs.
- gkfasdfasdf 6y agoValgrind can prohibitively slow down your process though, where many timing dependent code paths aren't hit and the app behaves dramatically different than it would in production.
- tinus_hn 6y ago‘Many’? Like what kind of code paths?
- gkfasdfasdf 6y agoReally any code that involves multiple threads, because there may be race conditions.