James Browning said: > I would be more concerned in the near and intermediate terms about the > possibility of allocating memory to pointer that already have associated > memory.
Right. But one way to find those is to fix the exit code to free everything so that anything left in use was a not-free-ed bug. Then valgrind can tell you about them and you can investigate. If the exit code doesn't free everything, you have to plow through all the legitimate leftovers. I think that will take too long to be practical. But we could iterate. Each time we find a legitmate leftover, fix the exit code to free it (and friends), then try again. The question is do we care enough about dangling blocks to fixup the free-on-exit code? -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org https://lists.ntpsec.org/mailman/listinfo/devel
