Tom Horsley writes:
On Tue, 13 Sep 2016 22:05:18 -0400
Sam Varshavchik wrote:
> [heap]
> 7 7fa2a0000000-7fa2a0085000 532.00 Kb rw-p 00000000 00:00 0
> 8 7fa2a0085000-7fa2a4000000 65004.00 Kb ---p 00000000 00:00 0
> 9 7fa2a8000000-7fa2a806f000 444.00 Kb rw-p 00000000 00:00 0
> 10 7fa2a806f000-7fa2ac000000 65092.00 Kb ---p 00000000 00:00 0
That looks like someone is doing heap protection by putting a inaccessible
section between each allocated heap chunk. There might be glibc malloc
debugging trigger of some kind to do that, but I wouldn't think
that would change just for the kernel version, so I'm out of ideas.
I recall that ElectricFence did something like that. But why even bother
mapping anything. I would think that accessing an unmapped region would
result in a SIGSEGV just as well.