This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Long-standing error in exception handling by pool_allocator (contains untested patch)
- From: Joachim Kuebart <kuebart at mathematik dot uni-ulm dot de>
- To: Paolo Carlini <pcarlini at suse dot de>
- Cc: Joachim Kuebart <kuebart at mathematik dot uni-ulm dot de>, libstdc++ at gcc dot gnu dot org
- Date: Mon, 11 Oct 2004 20:16:18 +0200
- Subject: Re: Long-standing error in exception handling by pool_allocator (contains untested patch)
- References: <20041009161531.GA653@jaja> <416833A4.6060609@suse.de> <4169545B.6070100@suse.de>
Hi Paolo,
On Sun, Oct 10, 2004 at 05:25:15PM +0200, Paolo Carlini wrote:
> The below is what I have just finished regtesting on x86/x86_64-linux.
> As you
> can see, I simply test that the fall back machinery originally designed
> by SGI/HP
> is actually working, instead of testing for memory corruption: the
> latter is more
> tricky, depends on too many parameters and risk to convey the misleading
> impression that the patch is "only" about memory corruption: in that
> case simply
> zeroing _S_start_free/_S_end_free before calling ::operator new would
> suffice.
Just wanted to tell you that your test works for my version of the
allocator (meaning it detects the problem and runs through after fixing
it). And you are right, it demonstrates the intended feature nicely.
Cheers,
cu Jo
--
La perfection est atteinte non quand il ne reste rien à ajouter, mais quand
il ne reste rien à enlever. (Antoine de Saint-Exupéry)