Finding space leaks should be easy: just let the program run until the space leak is huge and obvious. Is it so easy that automated tools could pinpoint the problem in the code, explain it, and fix it?
I unfortunately ran into another (Dodgem) space leak which only occurred when compiled with optimization.
No comments :
Post a Comment