Very good advice. I assume my C code does have memory blunders until I have run extensively through valgrind, after which I might begin to believe any other ana

Very good advice. I assume my C code does have memory blunders until I have run extensively through valgrind, after which I might begin to believe any other analysis I have done that suggests the code is correct. I also tend to test a build linked with gcc’s mudflap: gcc -g -fmudflap -lmudflap Your program will run much faster than under valgrind. I have had bugs that have been missed by valgrind but caught with mudflap and vice-versa. Don’t try to link with mudflap and run under valgrind at the same time though, valgrind won’t work.