svn_error_compose and (potential) memory leaks

The latest changes in the error functions is nice, but I think I found a
potential problem. When we create a new error, we reuse the child's pool
or create a new one; and that's fine, becsue it means that
svn_error_clear only has to destroy the first pool it gets it hands on
-- which is exactly what it does.

Except when we call svn_error_compose to splice two errors together.
When that happens (I count six places right now), we get a chain of
errors that aren't all allocated from the same pool, which means that
svn_error_clear is bound to leak memory.

Any ideas how to fix this? I'd thought about splicing the pool
hierarchy, but that sounds like a bit of a cruddy hack.

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org