On Thu, 21 Apr 2016, KatolaZ wrote: > Before going into finding gcc bugs, my humble suggestion is to give > a go to valgrind.
It is a wise suggestion. All GNU C/C++ programmers should have several passes through valgrind on their code, this is should be perceived as a standard procedure. Profiling with gprof is also recommended. Our resident programmer :^) Edbarx has noticeably improved the code of the netman application right after a few valgrind passes. never get out without valgrind ;^) ciao _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
