Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!feeder.erje.net!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Miles Bader Newsgroups: comp.lang.c++ Subject: Re: Memory Leak Detection Date: Wed, 14 Sep 2011 13:33:48 +0900 Organization: NEC Electronics Lines: 23 Message-ID: References: <7be371ee-c86c-4686-adbb-d0f3f716cde9@j1g2000yqn.googlegroups.com> <1073300f-64a0-4665-9e6e-a5000808b407@z7g2000vbp.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain X-Trace: individual.net tUW/yQJ79fvHO/WU/AVRsQbNia4eFsgFOJX6n3VmmzRwHHU66t Cancel-Lock: sha1:s/SPfhglcKWqdGfkce606FAvpA4= sha1:RJhJHyLRWcOXmJb2pHgpEHFW200= System-Type: x86_64-unknown-linux-gnu Blat: Foop Xref: x330-a1.tempe.blueboxinc.net comp.lang.c++:10091 "AnonMail2005@gmail.com" writes: > On Linux, I've used valgrind to track down memory leaks. It's very > good and it cost nothing. > > It is well worth the time investment (1/2 day) to learn how to use > it. After that, you will be pleasantly surprised at what it catches - > both large and small issues. Yes, valgrind is an insanely great tool. Not only is it super useful in tracking down the cause of bugs that manifest elsewhere, it allows one to be proactive and find many obscure subtle bugs that _haven't_ manifested elsewhere -- all without much user effort! [Running valgrind on a program for the first time can be a rude shock though, revealing tons of little bugs that you never noticed before!] -Miles -- Electricity, n. The cause of all natural phenomena not known to be caused by something else.