Hey all, what do you think about handling VALGRIND_MEMPOOL_ALLOC/FREE like normal allocations in massif? This works nicely for pool allocators that use mmap directly, instead of using malloc. For pools that use malloc, it will break as it will then in the worst-case report the duplicate memory consumption (once the block allocation, then all individual allocations in that block).
Still, I think that would be a good idea to have, at least optionally with an off-by-default cli switch. I have it tested locally, it is trivial to patch Valgrind's massif to do that and I'd be happy to spent more time on making it configurable if there's interest. What do you think? -- Milian Wolff m...@milianw.de http://milianw.de ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
