Thanks all for the input . I'm definitely not ready to call it a bug, and always suspect my code first, but this is a new one on me and I'm stumped. You have given me new avenues to explore, and I am most appreciative.
SWS On Thu, Apr 21, 2016 at 3:06 PM, Jaromil <jaro...@dyne.org> wrote: > 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 > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng >
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
