<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.newlc.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>NewLC - Looking for Memory Leak Advice - Comments</title>
 <link>http://www.newlc.com/forum/looking-memory-leak-advice</link>
 <description>Comments for &quot;Looking for Memory Leak Advice&quot;</description>
 <language>en</language>
<item>
 <title>Re: Looking for Memory Leak Advice</title>
 <link>http://www.newlc.com/forum/looking-memory-leak-advice#comment-42351</link>
 <description>&lt;p&gt;For symbian development, there is an excellent tool called &quot;HookLogger&quot;.&lt;/p&gt;

&lt;p&gt;It will log all memory allocations and deallocations and save the call stack for each allocation, so you easily can find what was responsible for the leak.&lt;/p&gt;

&lt;p&gt;The same approach ofcourse works for any platform, though I don&#039;t know of any tool names for other platforms.&lt;br /&gt;
&lt;/p&gt;</description>
 <pubDate>Wed, 17 Oct 2007 10:54:21 +0200</pubDate>
 <dc:creator>alh</dc:creator>
 <guid isPermaLink="false">comment 42351 at http://www.newlc.com</guid>
</item>
<item>
 <title>Looking for Memory Leak Advice</title>
 <link>http://www.newlc.com/forum/looking-memory-leak-advice</link>
 <description>&lt;p&gt;Apart from buying BoundsChecker or any of the other tools to track down memory leaks.  Does anyone have any advice or tips from your years of programming experience to offer on how to track down the causes of memory leaks?&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://www.newlc.com/forum/looking-memory-leak-advice&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.newlc.com/forum/looking-memory-leak-advice#comments</comments>
 <category domain="http://www.newlc.com/forums/microsoft-visual-c-net">Microsoft Visual C++ / Carbide.vs</category>
 <pubDate>Wed, 17 Oct 2007 00:39:15 +0200</pubDate>
 <dc:creator>Captain Xarzu</dc:creator>
 <guid isPermaLink="false">19324 at http://www.newlc.com</guid>
</item>
</channel>
</rss>
