On Mon, May 20, 2002 at 02:17:14PM +0100, Mark Fowler wrote:
> I was hoping more for a pointer to "Top Ten Memory Leaks in Various perls
> And What To Do About Them" page.
As you summarised, I think that number 1 is "failed eval".
I'm not sure what the rest are.
The solution to most of the rest is "upgrade to 5.8" because I think most
of the rest have (if not all the known ones) have been squashed.
What to do is either:
1: Buy Alan Burlison beer
(or some other way of saying thank you for attacking perl with purify
and doing a lot of the cleanup)
[buy beer in the hope that he carries on]
2: Play with purify, or more likely fun free tools such as valgrind:
http://developer.kde.org/~sewardj/
(valgrind++)
[while on the subject of ++, ccache++ : http://ccache.samba.org/ ]
and find the leaks.
Doesn't matter if you can't fix them - just make short test scripts
and bug report them.
er, not sure what else
failed eval is unlikely to go away before perl6, as (if I understand it
correctly) yacc has this fundamental assumption that if it fails your
syntax, the program is going to exit anyway, so no need to waste time
freeing up memory.
Nicholas Clark
