mmap memory allocation - do not used when under valgrind
authorCarsten Haitzler (Rasterman) <raster@rasterman.com>
Thu, 11 Jan 2018 17:59:34 +0000 (02:59 +0900)
committerWonki Kim <wonki_.kim@samsung.com>
Wed, 17 Jan 2018 09:19:28 +0000 (18:19 +0900)
commit0f33734b5d4e36931a4bb261ad8996310561d65e
tree7d93b5f5e709a282b7955de96feb511415f765c5
parente45e592c3e17a9fb58864d0d2d0175e3c95c5688
mmap memory allocation - do not used when under valgrind

we can't sensibly use things like massif to track memory if we bypass
itr with mmaping -1 fd anonymous memory... so if built with valgrind
support and running under valgrind, use malloc/calloc and free so
these tools actually do something useful for these bits of memory.
src/lib/eina/eina_debug_chunk.c
src/lib/eina/eina_evlog.c
src/lib/eina/eina_safepointer.c
src/lib/eo/eo.c
src/lib/eo/eo_add_fallback.c
src/lib/eo/eo_ptr_indirection.x
src/lib/evas/common/evas_image_main.c