<?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 16)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2010/02/13/trace-analysis-patterns-part-16/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Tue, 19 May 2026 07:10:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Adjoint threads, discontinuity and time delta: software trace pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2010/02/13/trace-analysis-patterns-part-16/#comment-137676</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Adjoint threads, discontinuity and time delta: software trace pattern cooperation</dc:creator>
		<pubDate>Wed, 24 Mar 2010 23:11:47 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2010/02/13/trace-analysis-patterns-part-16/#comment-137676</guid>
		<description>[...] PID for print spooler process (19984) and immediately see discontinuity in the trace with the large time delta between the last PID message and the last trace statement (almost 4 [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] PID for print spooler process (19984) and immediately see discontinuity in the trace with the large time delta between the last PID message and the last trace statement (almost 4 [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
