Garrett Rooney wrote:
On 12/22/05, Marco Spinetti <[EMAIL PROTECTED]> wrote:
Any advice?
I compiled apr with enable pool debug = verbose.
Now in the error log I have a lot of information.
How can I discover apr memory problems by these information?
Because of apr is so much powerful I suppose that there is some way to
debug it.....
There are some instructions on
http://subversion.tigris.org/hacking.html#tracing-memory-leaks that
explain how we've tracked down pool allocation problems in Subversion.
Perhaps they'll be helpful for your problem.
I also wrote some scripts to graph them:
http://paul.querna.org/journal/articles/2005/02/23/apr-memory-pools-rock
But, I don't know if they even work anymore. I wish I had time to make
them.. better.
-Paul
