<?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 77)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2008/10/21/crash-dump-analysis-patterns-part-77/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Sat, 06 Jun 2026 23:09:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/10/21/crash-dump-analysis-patterns-part-77/#comment-764864</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Mon, 01 Feb 2021 09:12:52 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/10/21/crash-dump-analysis-patterns-part-77/#comment-764864</guid>
		<description>How to get exception information from exception record: 
https://devblogs.microsoft.com/oldnewthing/20200821-00/?p=104112</description>
		<content:encoded><![CDATA[<p>How to get exception information from exception record:<br />
<a href="https://devblogs.microsoft.com/oldnewthing/20200821-00/?p=104112" rel="nofollow">https://devblogs.microsoft.com/oldnewthing/20200821-00/?p=104112</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/10/21/crash-dump-analysis-patterns-part-77/#comment-186760</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sun, 26 Sep 2010 09:34:03 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/10/21/crash-dump-analysis-patterns-part-77/#comment-186760</guid>
		<description>There is also !cppexr command</description>
		<content:encoded><![CDATA[<p>There is also !cppexr command</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; On Self Dumps of Secure String API</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/10/21/crash-dump-analysis-patterns-part-77/#comment-84703</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; On Self Dumps of Secure String API</dc:creator>
		<pubDate>Tue, 14 Jul 2009 17:36:19 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/10/21/crash-dump-analysis-patterns-part-77/#comment-84703</guid>
		<description>[...] that is similar to Self-Dump pattern here. The same parameter checking is seen in the case of C++ STL exceptions. In case of custom unhandled exception filters not resorting to WER faulrep.dll other stacks can [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] that is similar to Self-Dump pattern here. The same parameter checking is seen in the case of C++ STL exceptions. In case of custom unhandled exception filters not resorting to WER faulrep.dll other stacks can [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Virtualized process, incorrect stack trace, stack trace collection, multiple exceptions, optimized code and C++ exception: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/10/21/crash-dump-analysis-patterns-part-77/#comment-83535</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Virtualized process, incorrect stack trace, stack trace collection, multiple exceptions, optimized code and C++ exception: pattern cooperation</dc:creator>
		<pubDate>Wed, 08 Jul 2009 19:54:14 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/10/21/crash-dump-analysis-patterns-part-77/#comment-83535</guid>
		<description>[...] we have found the 3rd-party component that raised e06d7363 C++ exception. Actually Internet search shows that e06d7363 is quite common in many [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we have found the 3rd-party component that raised e06d7363 C++ exception. Actually Internet search shows that e06d7363 is quite common in many [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Stack trace collection, message box, hidden exception, nested offender, insufficient memory, C++ exception, heap leak and ubiquitous component: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/10/21/crash-dump-analysis-patterns-part-77/#comment-81079</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Stack trace collection, message box, hidden exception, nested offender, insufficient memory, C++ exception, heap leak and ubiquitous component: pattern cooperation</dc:creator>
		<pubDate>Thu, 25 Jun 2009 00:18:18 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/10/21/crash-dump-analysis-patterns-part-77/#comment-81079</guid>
		<description>[...] from it see the real nested offender that experienced insufficient memory condition resulted in C++ exception. You can see WinDbg output from this dump in the post about Nested Offender pattern (I don&#8217;t [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] from it see the real nested offender that experienced insufficient memory condition resulted in C++ exception. You can see WinDbg output from this dump in the post about Nested Offender pattern (I don&#8217;t [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
