https://bugs.kde.org/show_bug.cgi?id=452802
--- Comment #10 from Paul Floyd <pjfl...@wanadoo.fr> --- OK, this is to do with how the ELF exe or shared lib gets loaded. There are 3 cases. 1. the tool itself, already loaded and we look at the maps and work backwards to get NSegments and dinfo. 2. The client (and interpreter). We read the ELF headers and do the loading afterwards. That means the NSegments are done before the mmaping and dinfo loading occurs. 3. Any client shared libraries. These get loaded by the interpreter when the client is running under the host, we intercept the mmap calls and add NSegments and mmap/dinfo. The problem is in point 2 when there is a merge of the NSegements. That will result in just one call to VG_(di_notify_mmap) for the merged segement. And VG_(di_notify_mmap) needs two calls when the ELF headers contain 2 RW PT_LOADs. Maybe I need to use both (looking at NSegments for client load, looking at the ELF headers for a shared lib load). In that case I need to know which context VG_(di_notify_mmap) is being called from. Mayb the elf header e_type could do that. -- You are receiving this mail because: You are watching all bug changes.
