<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: I&#8217;m RARE</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2008/10/28/im-rare/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 10:32:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Looking for abnormal: case study</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/10/28/im-rare/#comment-72306</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Looking for abnormal: case study</dc:creator>
		<pubDate>Mon, 27 Apr 2009 10:22:03 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/10/28/im-rare/#comment-72306</guid>
		<description>[...] I’m RARE rule #5 says: &#8220;Provide appropriate explanations and narrative in the cases where analysis is inconclusive&#8221;. Here is the typical example of such case when a kernel dump was taken with the vague description about server problems. The dump file analysis revealed the following abnormal conditions warranting further troubleshooting steps: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I’m RARE rule #5 says: &#8220;Provide appropriate explanations and narrative in the cases where analysis is inconclusive&#8221;. Here is the typical example of such case when a kernel dump was taken with the vague description about server problems. The dump file analysis revealed the following abnormal conditions warranting further troubleshooting steps: [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
