Stafford Horne a817b1b5f4 e/core: Fix minor mem leak when reading module paths ... Summary: Found this with a quick valgrind session. For paths that are not directories, if we fail the `ecore_file_is_dir` condition memory will not be freed. The change is to use the default e_path freeing function. Test Plan: Run enlightenment in valgrind. It should no longer show a mem leak like below. ``` ==6912== 8 bytes in 1 blocks are definitely lost in loss record 186 of 5,940 ==6912== at 0x4C28C50: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==6912== by 0x4D8574: e_path_dir_list_get (e_path.c:326) ==6912== by 0x4D1BA4: e_module_init.part.0 (e_module.c:183) ==6912== by 0x4D1DA8: e_module_init (e_module.c:153) ==6912== by 0x4371ED: main (e_main.c:868) ``` Reviewers: zmike Subscribers: cedric, seoz Differential Revision: https://phab.enlightenment.org/D3356		2015-12-04 16:00:36 -05:00
..
bin	e/core: Fix minor mem leak when reading module paths	2015-12-04 16:00:36 -05:00
modules	block task gadget refills while a drag is active	2015-12-04 16:00:36 -05:00
tests	add basic fullscreen window test	2015-08-20 16:54:01 -04:00
Makefile.mk	feature: use non-recursive makefiles for entire build system	2014-01-14 20:22:01 -05:00