<?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: Crash Dump Analysis AntiPatterns (Part 5)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2007/11/01/crash-dump-analysis-antipatterns-part-5/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 08:18:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: TomM</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/01/crash-dump-analysis-antipatterns-part-5/#comment-9711</link>
		<dc:creator>TomM</dc:creator>
		<pubDate>Thu, 01 Nov 2007 11:29:05 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/01/crash-dump-analysis-antipatterns-part-5/#comment-9711</guid>
		<description>A antipattern not is only relevant to dump analysis but to troubleshooting in general.

The best approach would be to take the benefits from both worlds where you thoroughly read the problem description but also be careful not to jump to assumptions. In this case the unverified assumption is that the dump is off a hung process and a manually triggered crash dump.</description>
		<content:encoded><![CDATA[<p>A antipattern not is only relevant to dump analysis but to troubleshooting in general.</p>
<p>The best approach would be to take the benefits from both worlds where you thoroughly read the problem description but also be careful not to jump to assumptions. In this case the unverified assumption is that the dump is off a hung process and a manually triggered crash dump.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
