Subject: Re: [boost] [simple_segregated_storage] segfault
From: Chris Newbold (Chris.Newbold_at_[hidden])
Date: 2008-10-02 14:02:55
> From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]]
> On Behalf Of Phil Bouchard
> Sent: Thursday, October 02, 2008 12:34 PM
> I will verify this but what I personaly get is a ordered_malloc() failure
> the 2005th attempt. 3 blocks of memory get allocated / deallocated over
> over until the allocation routine fails.
If unchecked, it eventually crashes for me inside of simple_segregated_storage::try_malloc_n(), which I believe is what you're seeing.
The stack trace I quoted in my previous e-mail is the trace of the errant write that corrupts the pool.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk