https://bugs.kde.org/show_bug.cgi?id=472409
--- Comment #15 from Paul Floyd <pjfl...@wanadoo.fr> --- When you run a compiled binary standalone, one of the first things that happens is that ld.so, the link loader, reads ELF information in your binary to see which dynamic libraries it links to, and it loads them. In order to load them it reads the ELF header and segments marked LOAD get loaded (via mmap) into memory. This can also be done on the fly by dlopen which results in the same thing happening (reading ELF headers and mmap'in LOAD segemnts). When you run your exe in Valgrind, all ofthe above still happen but running under Valgrind. The Valgrind memory manager maintains a list of mapped memory blocks. This gets updated whenever Valgrind sees a file get mmap'd. In this case, when the exe does a mmap, Valgrind is trying to read the ELF header so that it can add the new segment to its internal list. The values that is sees for the offset and size are incoherent - the segments shouldn't be overlapping but they are in this case. -- You are receiving this mail because: You are watching all bug changes.
