<?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>.NET Finalizer Memory Leak: Debugging with sos.dll in Visual Studio</title><link>http://blogs.msdn.com/tess/archive/2007/10/19/net-finalizer-memory-leak-debugging-with-sos-dll-in-visual-studio.aspx</link><description>Normally I write about issues that only manifest themselves in production environment, issues that you can't really reproduce in a controlled dev environment every time you perform a certain action. In those cases you need to use tools like windbg to</description><dc:language>sv-SE</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: .NET Finalizer Memory Leak: Debugging with sos.dll in Visual Studio</title><link>http://blogs.msdn.com/tess/archive/2007/10/19/net-finalizer-memory-leak-debugging-with-sos-dll-in-visual-studio.aspx#5525242</link><pubDate>Fri, 19 Oct 2007 18:42:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5525242</guid><dc:creator>Peter Ritchie</dc:creator><description>&lt;p&gt;Maybe I misundestood the context when you said &amp;quot;Visual Studio on the other hand doesn't allow you to do post-mortem debugging&amp;quot;. &amp;nbsp;The following are a sample couple of links that describe post-mortem (crash dump) debugging with Visual Studio:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://msdn2.microsoft.com/en-us/library/d5zhxt22.aspx"&gt;http://msdn2.microsoft.com/en-us/library/d5zhxt22.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.codeproject.com/debug/postmortemdebug_standalone1.asp"&gt;http://www.codeproject.com/debug/postmortemdebug_standalone1.asp&lt;/a&gt;&lt;/p&gt;</description></item><item><title>re: .NET Finalizer Memory Leak: Debugging with sos.dll in Visual Studio</title><link>http://blogs.msdn.com/tess/archive/2007/10/19/net-finalizer-memory-leak-debugging-with-sos-dll-in-visual-studio.aspx#5526603</link><pubDate>Fri, 19 Oct 2007 20:31:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5526603</guid><dc:creator>mcgurk</dc:creator><description>&lt;p&gt;Reading your posts is like passing by a horrible car wreck. &amp;nbsp;You know you don't want anything to do with what's going on in the crash scene, but goddamn if you don't have to take a peek. &amp;nbsp;Also, you never want to be in the middle of one of them... but you might.&lt;/p&gt;</description></item><item><title>Link Listing - October 19, 2007</title><link>http://blogs.msdn.com/tess/archive/2007/10/19/net-finalizer-memory-leak-debugging-with-sos-dll-in-visual-studio.aspx#5535679</link><pubDate>Sat, 20 Oct 2007 06:39:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5535679</guid><dc:creator>Christopher Steen</dc:creator><description>&lt;p&gt;NoVa Code Camp 2007.02 [Via: Jeff Schoolcraft ] EarthClassMail.com - Moving from LAMP to .NET 3.5 [Via:...&lt;/p&gt;
</description></item><item><title>re: .NET Finalizer Memory Leak: Debugging with sos.dll in Visual Studio</title><link>http://blogs.msdn.com/tess/archive/2007/10/19/net-finalizer-memory-leak-debugging-with-sos-dll-in-visual-studio.aspx#5592156</link><pubDate>Mon, 22 Oct 2007 09:10:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5592156</guid><dc:creator>Tess</dc:creator><description>&lt;p&gt;Thanks mcgurk, &lt;/p&gt;
&lt;p&gt;That would have to be the weirdest compliment I've ever gotten:)&lt;/p&gt;
</description></item><item><title>re: .NET Finalizer Memory Leak: Debugging with sos.dll in Visual Studio</title><link>http://blogs.msdn.com/tess/archive/2007/10/19/net-finalizer-memory-leak-debugging-with-sos-dll-in-visual-studio.aspx#5592352</link><pubDate>Mon, 22 Oct 2007 09:26:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5592352</guid><dc:creator>Tess</dc:creator><description>&lt;p&gt;Hi Peter,&lt;/p&gt;
&lt;p&gt;No you didnt missunderstand, I just phrased it wrong... &lt;/p&gt;
&lt;p&gt;You can do limited dump analysis in visual studio, and to be honest it works pretty good, but given how hard it is to get to the native parts and run commands like ~* &amp;nbsp;etc. it's almost a can't. &amp;nbsp; &lt;/p&gt;
&lt;p&gt;I'll edit the post to reflect this... thanks for the comment... &lt;/p&gt;
</description></item><item><title>re: .NET Finalizer Memory Leak: Debugging with sos.dll in Visual Studio</title><link>http://blogs.msdn.com/tess/archive/2007/10/19/net-finalizer-memory-leak-debugging-with-sos-dll-in-visual-studio.aspx#5691970</link><pubDate>Fri, 26 Oct 2007 17:16:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5691970</guid><dc:creator>jigarme@live.com</dc:creator><description>&lt;p&gt;SOSAssist saved my life.&lt;/p&gt;
&lt;p&gt;Thanks for sharing it!&lt;/p&gt;</description></item><item><title>re: .NET Finalizer Memory Leak: Debugging with sos.dll in Visual Studio</title><link>http://blogs.msdn.com/tess/archive/2007/10/19/net-finalizer-memory-leak-debugging-with-sos-dll-in-visual-studio.aspx#5844083</link><pubDate>Fri, 02 Nov 2007 23:34:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5844083</guid><dc:creator>nativecpp</dc:creator><description>&lt;p&gt;Just one question:&lt;/p&gt;
&lt;p&gt;Why can we 'load' some internal windbg from VS so that we can execute some useful windbg commands ?&lt;/p&gt;</description></item><item><title>Slides and resources for TechED presentations about debugging .NET issues with Windbg</title><link>http://blogs.msdn.com/tess/archive/2007/10/19/net-finalizer-memory-leak-debugging-with-sos-dll-in-visual-studio.aspx#9131620</link><pubDate>Fri, 21 Nov 2008 12:37:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9131620</guid><dc:creator>If broken it is, fix it you should</dc:creator><description>&lt;p&gt;I still have to figure out a way to host the video from the break-out session but until then, here are&lt;/p&gt;
</description></item></channel></rss>