Pools and errors

So, we have a fancy error-handling framework which involves
potentially allocating a linked list as we crawl up the stack. At the
same time, we have a fancy memory management framework which involves
potentially creating sub-pools to do temporary allocations in and
destroying them when we finish our work.

I am concerned by the potential for conflict here. In many cases, you
may not have a pool available to you which will live as long as the
error has to live. In other cases, you may only have a pool available
which lasts much longer than the error has to live, which could lead
to memory leaks. And in general, you can't even identify these cases,
much less address them.

Has anyone thought about this issue?
Received on Sat Oct 21 14:36:08 2006