From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,28f99e97a239682a X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!news3.google.com!proxad.net!feeder1-2.proxad.net!news.in2p3.fr!in2p3.fr!not-for-mail From: xavier grave Newsgroups: comp.lang.ada Subject: Re: Link gnat with "purify" to try to find a memory leak Date: Mon, 29 Sep 2008 10:32:21 +0200 Organization: In2p3 Message-ID: References: <0a839a05-adfc-4669-b0b5-47ae3c15b238@s50g2000hsb.googlegroups.com> NNTP-Posting-Host: ipnnarval.in2p3.fr Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ccpntc8.in2p3.fr 1222677207 358 134.158.92.7 (29 Sep 2008 08:33:27 GMT) X-Complaints-To: newsmaster@cc.in2p3.fr NNTP-Posting-Date: Mon, 29 Sep 2008 08:33:27 +0000 (UTC) User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724) In-Reply-To: <0a839a05-adfc-4669-b0b5-47ae3c15b238@s50g2000hsb.googlegroups.com> X-Enigmail-Version: 0.95.0 Xref: g2news1.google.com comp.lang.ada:2129 Date: 2008-09-29T10:32:21+02:00 List-Id: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 FJCS_Montecoruto a �crit : > Hi all, > > A "memory leak" has been detected in one of our Gnat-Ada/GtkAda > executables. I was directed with others to try to find where exactly > is it located in our code. > > Is it possible to somehow use "Rational Purify", to link it with our > Gnat-Ada/GtkAda objects, and so generate some instrumentalized > executable to run and test it under "Purify" ?. > > If so, is there an "easy way" to be able to do it ?. We have tried, > but we have had a hard time linking the objects. > > (I am also aware we have "gnatmem" available to confirm the leakage, > which we did. But now we would need to isolate the problem more > precisely, in the middle of a big lot of source code lines ). > > Any help appreciated, > Thank you, > FJCS Hi, I'm not used to purify, but I had a similar problem and I solved it using valgrind. My command looks like this : valgrind --tool=memcheck --leak-check=full --show-reachable=yes -v executable_name or the same plus : --log-socket=127.0.0.1:12345 if you want to use valgrind-listener Hope it will help, xavier -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjgkpMACgkQVIZi0A5BZF7M/gCfeXdz88nSVHaTjb/guwCXBA6G 260AnjKK1gOwLoox+/FHvm7z84DmJhev =x8Gg -----END PGP SIGNATURE-----