Subject: Re: [Boost-users] [pool] singlton_pool::malloc returning bad address
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2009-07-02 15:44:51
AMDG
Jonathan Leonard wrote:
> 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?
>
Are you only calling malloc and free or are you using other
singleton_pool function like malloc_n?
What version of Boost are you using?
In Christ,
Steven Watanabe