02-19-04 09:34 AM
In article <db9bbf31.0402190908.40d37ed6@posting.google.com>, qazmlp wrote:
> Memory leaks are found often in our C++ application which is running
> on Solaris machine. So, it was decided to link with libgc.so which
> comes with Solaris.
I'd say you should try rather hard with some memory leak finding
tool, and plug those rather.
> Before start doing that, I would want to know your
> experiences/thoughts/suggestions on using this library.
> - Will this really fix all memory leaks in a C/C++ application?
Often. Not guaranteed though.
> What are the leaks that can still escape from this?
Leaks that arn't true leaks. e.g. still keeping a pointer
to something you really should have disposed long ago.
> - Will it cause any performance impacts ie. reducing the existing
> performance
> in a time critical application?
malloc and especially free can take substancial longer time now.
> - Any other things that we have to take care?
>
> Kindly pour in your suggestions.
--
Vennlig hilsen/Best Regards
Nils Olav Selåsdal
System Engineer
w w w . u t e l s y s t e m s . c o m
[ Post a follow-up to this message ]
|