Hi Gustavo, On 3 December 2016 at 08:17, Gustavo Sverzut Barbieri <barbi...@gmail.com> wrote:
> barbieri pushed a commit to branch master. > > http://git.enlightenment.org/core/efl.git/commit/?id=227463b > dde43bc9095b75f4ef19f9fef9a742f04 > > commit 227463bdde43bc9095b75f4ef19f9fef9a742f04 > Author: Gustavo Sverzut Barbieri <barbi...@profusion.mobi> > Date: Fri Dec 2 20:48:37 2016 -0200 > > eo: allow valgrind-like tracking of object lifecycle. > > Eo pointer indirection is super nice as it avoids you to access > invalid memory, but this extra checks inhibits valgrind's own tracking > of memory lifecycle, usually it would report when the object was > created and when the object is deleted, both as stack traces. > > This commits introduces logging of object creation and destruction > under its own eina_log_domain and controlled by EO_LIFECYCLE_DEBUG and > EO_LIFECYCLE_NO_DEBUG envvars. These will only be available if > compiled with EO_DEBUG, thus shouldn't cause any performance hits on > production code. > So this should basically be used in conjunction with the existing eo_debug infrastructure? Why not improve eo_debug itself? (eg. add options to the script) > [snap] Best regards, -- Jean-Philippe André ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
