From: Lothar Scholz <mailinglists@...>
Date: 2003-09-18T08:22:30+09:00
Subject: Re: Testing for memory leaks

Hello Daniel,

Wednesday, September 17, 2003, 10:38:24 PM, you wrote:

BD> Testing for memory leaksHi all,

BD> Being as I write a lot of extensions, I've discovered that
BD> it's best to check for memory leaks.� The way I'm doing this now
BD> is something like this:

BD> Is there a better and/or more streamlined way to do this?�
BD> Any chance of adding assert_no_memory_leak to TestUnit, for
BD> example?

One of the best ways to detect memory leaks is to add the Boehm GC in
"leak report mode" to your app. This does not find everything but it
should be very easy to recompile with this enabled. Or search source
forge for the zillions of memory debugging libraries.

I'm not sure if ruby does free everything on normal exit. If not you
get some real problems with all this tools.

I would highly recommend to create a debugging ruby library and a
normal ruby library. There are much more things that could be added to
the debugging version at the C core level.

-- 
Best regards,
 Lothar                            mailto:mailinglists@scriptolutions.com