Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
MIME-Version: 1.0
In-Reply-To: <20170422061525.GA20756@jurassic>
Message-ID: <rt-4.4.1-40134-1506638752-844.45123-0-0@isc.org>
X-Mailer: MIME-tools 5.508 (Entity 5.508)
X-RT-Interface: Web
X-RT-Original-Encoding: utf-8
References: <20170422061525.GA20756@jurassic> <RT-Ticket-45123@isc.org>
RT-Send-CC:
Content-Length: 329

Just a thought (and a too late thought), but instead of doing a custom code, we can just use AddressSanitizer poisoning and let the ASAN do it's job:

https://github.com/google/sanitizers/wiki/AddressSanitizerManualPoisoning

This would make the code simpler, more standard and allow us to use ASAN to work on the custom mempool.