https://bugs.kde.org/show_bug.cgi?id=470244
--- Comment #2 from Simon <victor.unitie...@icloud.com> --- Its a bug because its not fully implementing the mmap() functionality.. However yes we are using mmap/mremap so that we don't change the base address of the mmap(). That appears to be in conflict with valgrind which is implemented along the lines of expecting malloc/free block style functionally. mmap() can be used in that fashion but its not the only way... We implement out out versions of malloc/free to use the memory pools which we allocate in this fashion. Looking at the valgrind source code I can see it would be a lot of work to implement mmap() style blocks.. Which is why I'm looking for work arounds as valgrind is a valuable tool for finding memory/file handle leaks. We currently we are enable to do. I've added the system trace as an attachment -- You are receiving this mail because: You are watching all bug changes.
