Hello. On 09/06/15 12:15, Carsten Haitzler wrote: > On Tue, 09 Jun 2015 10:38:03 +0200 Stefan Schmidt <ste...@osg.samsung.com> > said: > >> Hello. >> >> I just run through some of the coverity issues and spotted some where i >> would the actual code author to have a look and either fix them or mark >> as false positive. >> >> First of all the 4 issues with potential high impact: >> >> 1304728 Resource leak >> <https://scan6.coverity.com:8443/docs/en/cov_checker_ref.html#static_checker_RESOURCE_LEAK> >> in eo_lexer.c (q66) >> 1297407 Resource leak >> <https://scan6.coverity.com:8443/docs/en/cov_checker_ref.html#static_checker_RESOURCE_LEAK> >> in eina_btlog.c (raster) > if you know what the binary does/is for... this is zero impact :)
Sure, it one time running for debugging and not a long time run thing like a lib or daemon. But Coverity has no idea about it. I just put it here as it was under the high impact items even if in reality is it zero impact for us. :) regards Stefan Schmidt ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
