> MEH: heaptrack_print | mmap: 56166e9d4000 56166ea39000 | dwfl: 56166e9d4000 > 56166ea38880 > MEH: ld-2.26.so | mmap: 7fd0afc6c000 7fd0afe93000 | dwfl: 7fd0afc6c000 > 7fd0afe920f8 > MEH: libc-2.26.so | mmap: 7fd0ae16a000 7fd0ae521000 | dwfl: 7fd0ae16a000 > 7fd0ae5208f0 > MEH: libstdc++.so.6.0.24 | mmap: 7fd0aea84000 7fd0aee0b000 | dwfl: > 7fd0aea84000 7fd0aee0a640 > MEH: libzstd.so.1.3.3 | mmap: 7fd0aee0b000 7fd0af087000 | dwfl: 7fd0aee0b000 > 7fd0af086030 > > Interestingly, here the mmap events observed by perf are actually always > *larger* than what dwfl sees...
Do those differences map to some specific ELF sections? That is, does elfutils assume some sections are mmap'd even though they aren't or vice versa? As elfutils always assumes pgoff == 0 it should be fairly simple to see which sections those are (right?). Ulf
