On 01/22/2014 09:21 PM, Dave Jones wrote:
> On Wed, Jan 22, 2014 at 09:16:03PM -0500, Sasha Levin wrote:
>   > On 01/22/2014 08:52 PM, Dave Jones wrote:
>   > > Sasha, is this the current git tree version of Trinity ?
>   > > (I'm wondering if yesterdays munmap changes might be tickling this bug).
>   >
>   > Ah yes, my tree has the munmap patch from yesterday, which would explain why we
>   > started seeing this issue just now.
>
> So that change is basically allowing trinity to munmap just part of a prior mmap.
> So it may do things like..
>
> mmap   |--------------|
>
> munmap |----XXX-------|
>
> munmap |------XXX-----|
>
> ie, it might try unmapping some pages more than once, and may even overlap prior munmaps.
>
> until yesterdays change, it would only munmap the entire mmap.
>
> There's no easy way to tell exactly what happened without a trinity log of course.

I've attached the trinity log of the child that triggered the bug. Odd thing is that I
don't see any munmaps in it.


Thanks,
Sasha