4 Oct
2008
4 Oct
'08
2:27 a.m.
"Chris Newbold" <Chris.Newbold@mathworks.com> wrote in message news:6F6A2FC198A0F943ACC2259C38A2E30B6B6FB4BDB1@EXCHANGE-AH.ad.mathworks.com...
From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org]
[...]
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.
I had a chance to run some tests quickly this morning; it turns out all deallocations with corresponding size are valid. -Phil