I'm working with some old perl code that was previously running under modperl 1.x, but was recently updated for 2.x. There is a fairly severe memory leak somewhere in this code, but I'm having a hell of a time tracking it down.
The problem is that I don't know which of our many perl files is causing the leak. I've tried setting up a test server and hitting the likely suspects with ab, but no dice so far. So, my question is: is there a way for me to figure out *which perl file* is causing the leak, without just manually testing every code path of every file? -Michael
