I'm only calling malloc() and free(). I'm also using tbb's scalable_allocator for non- O-O allocations (if that would matter). This is with boost 1.37. --Jonathan -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Steven Watanabe Sent: Thursday, July 02, 2009 12:45 PM To: boost-users@lists.boost.org Subject: Re: [Boost-users] [pool] singlton_pool::malloc returning bad address 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 _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users