[DynInst_API:] [dyninst/dyninst] 0febdb: RT: trymmap should retry if the result is out of r...


Date: Tue, 15 Nov 2016 10:01:54 -0800
From: Bill Williams <wwilliam47@xxxxxxxxx>
Subject: [DynInst_API:] [dyninst/dyninst] 0febdb: RT: trymmap should retry if the result is out of r...
  Branch: refs/heads/master
  Home:   https://github.com/dyninst/dyninst
  Commit: 0febdb8e2ad94a354000c3d4f36be8e51a3d2493
      https://github.com/dyninst/dyninst/commit/0febdb8e2ad94a354000c3d4f36be8e51a3d2493
  Author: Josh Stone <jistone@xxxxxxxxxx>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M dyninstAPI_RT/src/RTheap.c

  Log Message:
  -----------
  RT: trymmap should retry if the result is out of range

An address passed to `mmap` is just taken as a hint, and the OS may
return something wildly different if that address is not available.
This is undesirable when we're trying to create a constrained alloc.

Now we will check that the address is in the requested range before
accepting it.  Otherwise, unmap it and try a new hint.


  Commit: d747211f84658f39010f13d066432bdb41627087
      https://github.com/dyninst/dyninst/commit/d747211f84658f39010f13d066432bdb41627087
  Author: Bill Williams <wwilliam47@xxxxxxxxx>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M dyninstAPI_RT/src/RTheap.c

  Log Message:
  -----------
  Merge pull request #231 from cuviper/constrain-trymmap-master

RT: trymmap should retry if the result is out of range


Compare: https://github.com/dyninst/dyninst/compare/dd930f832016...d747211f8465
[← Prev in Thread] Current Thread [Next in Thread→]
  • [DynInst_API:] [dyninst/dyninst] 0febdb: RT: trymmap should retry if the result is out of r..., Bill Williams <=