I am all for moving ahead.
I was checking out another application with `valgrind` on Ubuntu 17.04
64-bit so thought I would give `qgis` a try eg.
valgrind --leak-check=full ./output/bin/qgis
Is this only with my build (simply entering and exiting the qgis
application) or does it affect anyone else? Are there better tools?
==4970== LEAK SUMMARY:
==4970== definitely lost: 6,832 bytes in 30 blocks
==4970== indirectly lost: 2,626 bytes in 114 blocks
==4970== possibly lost: 1,600,902 bytes in 6,208 blocks
==4970== still reachable: 5,589,841 bytes in 51,784 blocks
==4970== of which reachable via heuristic:
==4970== length64 : 149,736 bytes in
227 blocks
==4970== newarray : 4,464 bytes in 6
blocks
==4970== multipleinheritance: 432 bytes in 3
blocks
==4970== suppressed: 0 bytes in 0 blocks
==4970== Reachable blocks (those to which a pointer was found) are not
shown.
==4970== To see them, rerun with: --leak-check=full
--show-leak-kinds=all
==4970==
==4970== For counts of detected and suppressed errors, rerun with: -v
==4970== Use --track-origins=yes to see where uninitialised values come
from
==4970== ERROR SUMMARY: 6451 errors from 358 contexts (suppressed: 0
from 0)
Gordon
_______________________________________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
