<?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>The Digital DNA of Bugs, Dump Analysis as Forensic Science</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/04/15/the-digital-dna-of-bugs-dump-analysis-as-forensic-science.aspx</link><description>Written by Jeff Dailey: As a debugger, have you ever reflected on the interesting parallels between your job and work being done in other industries? When I think about solving complex computer problems, I think of it as forensics. The core diagnostics</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Microsoft news and tips &amp;raquo; The Digital DNA of Bugs, Dump Analysis as Forensic Science</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/04/15/the-digital-dna-of-bugs-dump-analysis-as-forensic-science.aspx#8397895</link><pubDate>Tue, 15 Apr 2008 19:45:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8397895</guid><dc:creator>Microsoft news and tips &amp;raquo; The Digital DNA of Bugs, Dump Analysis as Forensic Science</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://microsoftnews.askpcdoc.com/?p=2581"&gt;http://microsoftnews.askpcdoc.com/?p=2581&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: The Digital DNA of Bugs, Dump Analysis as Forensic Science</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/04/15/the-digital-dna-of-bugs-dump-analysis-as-forensic-science.aspx#8397910</link><pubDate>Tue, 15 Apr 2008 19:49:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8397910</guid><dc:creator>Brad</dc:creator><description>&lt;P&gt;Nice post Jeff, thanks for taking the time to share.&lt;/P&gt;
&lt;P&gt;For high CPU, I usally start with perfmon and see if its one thread or a whole bunch. &amp;nbsp;If it's just one I can go int the debugger and see what that thread is doing or use kernrate to get a more full picture.&lt;/P&gt;
&lt;P&gt;I guess thats the difference between doing live debugging here in MSIT and doing remote debugging through PSS/CPR...&lt;/P&gt;</description></item></channel></rss>