<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Debugging memory usage in managed code using Windbg</title><link>http://blogs.msdn.com/kristoffer/archive/2007/01/09/debugging-memory-usage-in-managed-code-using-windbg.aspx</link><description>Windbg, is there anything it can't do? CLR Profiler is great for getting an overview of memory allocations and usage for managed applications but it doesn't work for very large applications and can't be attached after the application has been running</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Interesting Finds: January 13, 2007</title><link>http://blogs.msdn.com/kristoffer/archive/2007/01/09/debugging-memory-usage-in-managed-code-using-windbg.aspx#1461773</link><pubDate>Sat, 13 Jan 2007 19:15:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1461773</guid><dc:creator>Jason Haley</dc:creator><description>&lt;br&gt;</description></item></channel></rss>