> From: ranier [mailto:[EMAIL PROTECTED] > Sent: Monday, June 30, 2003 5:28 AM
> I read a Steve Maguire book named "Guia Microsoft para o desenvolvimento > de programas > sem erros" [ironic not?] and add some ideas for debugging memory > allocation in apr_pool.c. > > 1. Memory not initialized or freed is trash, on debug force this! > 2. Use intensive of the function "assert" on debug development. Using pools debug mode in combination with tools like valgrind have worked wonders. I personally don't think this will add extra value. Sander
