<?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 100)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2010/07/06/crash-dump-analysis-patterns-part-100/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Tue, 19 May 2026 05:33:44 +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/2010/07/06/crash-dump-analysis-patterns-part-100/#comment-741671</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Tue, 12 May 2015 22:01:37 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2010/07/06/crash-dump-analysis-patterns-part-100/#comment-741671</guid>
		<description>Another example: 

002afcd0 765614ab ntdll!ZwWaitForSingleObject+0x15
002afd3c 768b1194 KERNELBASE!WaitForSingleObjectEx+0x98
002afd54 768b1148 kernel32!WaitForSingleObjectExImplementation+0x75
002afd68 002e95de kernel32!WaitForSingleObject+0x12
WARNING: Stack unwind information not available. Following frames may be wrong.
002afd9c 767c8336 HookA+0x95de
002afdcc 767b80a9 USER32!DispatchHookA+0x10e
002afe0c 767c2bfd USER32!CallHookWithSEH+0x21
002afe3c 775b010a USER32!__fnHkINLPMOUSEHOOKSTRUCTEX+0x29
002afed4 00471c64 ntdll!KiUserCallbackDispatcher+0x2e
002afefc 00471d1f ProcessA+0x62d60
[...]
002aff94 775d9f72 kernel32!BaseThreadInitThunk+0xe
002affd4 775d9f45 ntdll!__RtlUserThreadStart+0x70
002affec 00000000 ntdll!_RtlUserThreadStart+0x1b</description>
		<content:encoded><![CDATA[<p>Another example: </p>
<p>002afcd0 765614ab ntdll!ZwWaitForSingleObject+0&#215;15<br />
002afd3c 768b1194 KERNELBASE!WaitForSingleObjectEx+0&#215;98<br />
002afd54 768b1148 kernel32!WaitForSingleObjectExImplementation+0&#215;75<br />
002afd68 002e95de kernel32!WaitForSingleObject+0&#215;12<br />
WARNING: Stack unwind information not available. Following frames may be wrong.<br />
002afd9c 767c8336 HookA+0&#215;95de<br />
002afdcc 767b80a9 USER32!DispatchHookA+0&#215;10e<br />
002afe0c 767c2bfd USER32!CallHookWithSEH+0&#215;21<br />
002afe3c 775b010a USER32!__fnHkINLPMOUSEHOOKSTRUCTEX+0&#215;29<br />
002afed4 00471c64 ntdll!KiUserCallbackDispatcher+0&#215;2e<br />
002afefc 00471d1f ProcessA+0&#215;62d60<br />
[&#8230;]<br />
002aff94 775d9f72 kernel32!BaseThreadInitThunk+0xe<br />
002affd4 775d9f45 ntdll!__RtlUserThreadStart+0&#215;70<br />
002affec 00000000 ntdll!_RtlUserThreadStart+0&#215;1b</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 111)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2010/07/06/crash-dump-analysis-patterns-part-100/#comment-197157</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 111)</dc:creator>
		<pubDate>Tue, 26 Oct 2010 21:22:16 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2010/07/06/crash-dump-analysis-patterns-part-100/#comment-197157</guid>
		<description>[...] the presence of the whole Pervasive System. It is not just a module that does function and / or message hooking but the whole system of modules from a single vendor that is context-aware (for example, [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] the presence of the whole Pervasive System. It is not just a module that does function and / or message hooking but the whole system of modules from a single vendor that is context-aware (for example, [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Models for Memory and Trace Analysis Patterns (Part 3)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2010/07/06/crash-dump-analysis-patterns-part-100/#comment-166376</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Models for Memory and Trace Analysis Patterns (Part 3)</dc:creator>
		<pubDate>Tue, 13 Jul 2010 15:56:33 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2010/07/06/crash-dump-analysis-patterns-part-100/#comment-166376</guid>
		<description>[...] we model Message Hooks pattern using MessageHistory tool. It uses window message hooking mechanism to intercept window [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we model Message Hooks pattern using MessageHistory tool. It uses window message hooking mechanism to intercept window [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
