<?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: Trace Analysis Patterns (Part 22)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2010/04/12/trace-analysis-patterns-part-22/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 04:45:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Trace Analysis Patterns (Part 30)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2010/04/12/trace-analysis-patterns-part-22/#comment-192725</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Trace Analysis Patterns (Part 30)</dc:creator>
		<pubDate>Wed, 13 Oct 2010 21:23:23 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2010/04/12/trace-analysis-patterns-part-22/#comment-192725</guid>
		<description>[...] Experts Magazine Online Sometimes, when we find an anchor message related to our problem description (for example, a COM port error) we are interested in its [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Experts Magazine Online Sometimes, when we find an anchor message related to our problem description (for example, a COM port error) we are interested in its [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Trace Analysis Patterns (Part 26)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2010/04/12/trace-analysis-patterns-part-22/#comment-174946</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Trace Analysis Patterns (Part 26)</dc:creator>
		<pubDate>Tue, 10 Aug 2010 15:27:20 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2010/04/12/trace-analysis-patterns-part-22/#comment-174946</guid>
		<description>[...] manifest itself visually. We can diagnose such traces by their short time duration, missing anchor messages or missing messages from components necessary for analysis. My favourite example is user session [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] manifest itself visually. We can diagnose such traces by their short time duration, missing anchor messages or missing messages from components necessary for analysis. My favourite example is user session [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Software Trace Analysis Tools: CDFMarker</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2010/04/12/trace-analysis-patterns-part-22/#comment-153729</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Software Trace Analysis Tools: CDFMarker</dc:creator>
		<pubDate>Tue, 25 May 2010 10:16:06 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2010/04/12/trace-analysis-patterns-part-22/#comment-153729</guid>
		<description>[...] This is useful in many troubleshooting scenarios where we need to rely on Significant Event and Anchor Message analysis patterns to partition traces into artificial Activity Regions to start our analysis with. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This is useful in many troubleshooting scenarios where we need to rely on Significant Event and Anchor Message analysis patterns to partition traces into artificial Activity Regions to start our analysis with. [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
