<?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>Crash Dump Analysis Patterns (Part 4)</title><link>http://blogs.msdn.com/kocoreinternals/archive/2008/09/17/crash-dump-analysis-patterns-part-4.aspx</link><description>Crash Dump Analysis 네번째 패턴에 대한 번역입니다. 간략히 설명을 드리자면, Part 4는 접하게 되었을 경우 선택의 여지가 별로 없는 상황입니다. Lateral Damage 패턴이라고 하는데, 받은 덤프에서 봐야할 중요 데이터들이 손상된 상황에서는 한번 다른 컴포넌트들(드라이버 후킹)을 살펴보라고 조언합니다. Crash Dump Analysis Patterns (Part 4) 원문링크 번역: 김희준( http://insidekernel.net</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>  Crash Dump Analysis Patterns (Part 4) : EasyCoded</title><link>http://blogs.msdn.com/kocoreinternals/archive/2008/09/17/crash-dump-analysis-patterns-part-4.aspx#8955181</link><pubDate>Wed, 17 Sep 2008 12:00:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8955181</guid><dc:creator>  Crash Dump Analysis Patterns (Part 4) : EasyCoded</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.easycoded.com/crash-dump-analysis-patterns-part-4/"&gt;http://www.easycoded.com/crash-dump-analysis-patterns-part-4/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>