Hi all,

In a long running process on Windows, I’m seeing singleton_pool::malloc eventually return addresses such as 0x100f34b0 (which in this case [according to vmmap] is an address into a ‘read-only’ section (.rdata) of a DLL which was loaded for ‘execute/copy on write’).  The system [rightly] barfs at the request to write to that address.

Anyone have an idea what could be going on here?

Many thanks,

Jonathan