<?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 Patterns (Part 67)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2008/06/24/crash-dump-analysis-patterns-part-67/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Mon, 18 May 2026 04:55:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Incorrect stack trace, stack overflow, early crash dump, nested exception, problem exception handler and same vendor: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/06/24/crash-dump-analysis-patterns-part-67/#comment-198592</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Incorrect stack trace, stack overflow, early crash dump, nested exception, problem exception handler and same vendor: pattern cooperation</dc:creator>
		<pubDate>Sat, 30 Oct 2010 23:19:29 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/06/24/crash-dump-analysis-patterns-part-67/#comment-198592</guid>
		<description>[...] Here we were able to get stack trace from the saved nested exception:  [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Here we were able to get stack trace from the saved nested exception:  [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Old Mental Dumps from June 24th</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/06/24/crash-dump-analysis-patterns-part-67/#comment-160702</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Old Mental Dumps from June 24th</dc:creator>
		<pubDate>Thu, 24 Jun 2010 11:29:48 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/06/24/crash-dump-analysis-patterns-part-67/#comment-160702</guid>
		<description>[...] Crash Dump Analysis Patterns (Part 67) - Nested Exception pattern. Appears also in the following case study: WOW64 process, NULL data [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Crash Dump Analysis Patterns (Part 67) - Nested Exception pattern. Appears also in the following case study: WOW64 process, NULL data [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; WOW64 process, NULL data pointer, stack overflow, main thread, incorrect stack trace, nested exceptions, hidden exception, manual dump, multiple exceptions and virtualized system: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/06/24/crash-dump-analysis-patterns-part-67/#comment-84352</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; WOW64 process, NULL data pointer, stack overflow, main thread, incorrect stack trace, nested exceptions, hidden exception, manual dump, multiple exceptions and virtualized system: pattern cooperation</dc:creator>
		<pubDate>Sun, 12 Jul 2009 16:59:00 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/06/24/crash-dump-analysis-patterns-part-67/#comment-84352</guid>
		<description>[...] consider this as a nested unmanaged exception and try to see where it originated. First we double check that we don&#8217;t have any exceptions [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] consider this as a nested unmanaged exception and try to see where it originated. First we double check that we don&#8217;t have any exceptions [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 86)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/06/24/crash-dump-analysis-patterns-part-67/#comment-80943</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 86)</dc:creator>
		<pubDate>Wed, 24 Jun 2009 09:14:16 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/06/24/crash-dump-analysis-patterns-part-67/#comment-80943</guid>
		<description>[...] Offender is different from Nested Exception pattern. The latter is about an exception handler that experiences or throws another [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Offender is different from Nested Exception pattern. The latter is about an exception handler that experiences or throws another [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 67b)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/06/24/crash-dump-analysis-patterns-part-67/#comment-31542</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 67b)</dc:creator>
		<pubDate>Wed, 25 Jun 2008 15:48:32 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/06/24/crash-dump-analysis-patterns-part-67/#comment-31542</guid>
		<description>[...] exception analysis is much simpler in managed code than in unmanaged. Exception object references the inner exception if any and so [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] exception analysis is much simpler in managed code than in unmanaged. Exception object references the inner exception if any and so [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
