On 06.06.2012 08:42, David Currie wrote: > Just run it with NO arguments at first then under valgrind with args > You'll get the idea.
[ test code elided ] > ON MY MACHINE level 2 causes an extra 3 bytes 3 blocks lost per testCount. I see this as well, looks strange. This should maybe be investigated further. Currently I don't have the time, but if you can do, I suggest to compile FLTK with debug enabled, so that valgrind can give more info about the calling functions - but I'm not sure if this works at all, since I don't have much experience with valgrind. I'd have to try it as well. > It doesnt get errors in ERROR SUMMARY until level 6. I'm also using Ubuntu (as you said, you're using), but I don't get errors at any level, *unless* I run valgrind "with --leak-check=full to see details of leaked memory", as the LEAK SUMMARY suggests. I'm surprised that this makes a difference - maybe a bug in valgrind? > It's possible that this isn't even an error. Yes, I think so, see last paragraph above. > But run it and give me an opinion. Well, most of the "leaks" (i.e. lost bytes/blocks) we can see result from initialisation code like fl_open_display() and are somewhere in X libraries. I wouldn't be concerned about these, particularly since they don't seem to grow during runtime (i.e. increased loop count). The only "interesting" thing would be the "extra 3 bytes 3 blocks lost per testCount" mentioned by you, but this is strange anyway. This would mean 3 blocks, with 1 byte per block, if I interpret this correctly. That sounds really strange... Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
