Re: [Valgrind-users] Memory leak not detected

[John R. <jr...@bi...>]

> I think I found the problem. It seems valgrind doesn't detect memory leaks related to mmap. Why is this the case?

A memory leak is a block that is allocated by malloc/calloc/realloc/reallocarray,
not yet free()d, and with no in-process pointers to it.
mmap is not malloc, and the result of mmap() cannot be a memory leak.
Run "strace -e trace=mmap,mmap2,munmap,mremap ./my_app args..."
or use a debugger to put a breakpoint on appropriate calls.