<?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 6a)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Tue, 19 May 2026 13:09:51 +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/04/28/crash-dump-analysis-patterns-part-6a/#comment-741758</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Sat, 20 Oct 2018 17:38:32 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/#comment-741758</guid>
		<description>Some runtime implementations replace NULL code pointers with some default functions which provide additional diagnostics, for example, in the case of C++ pure virtual call:

&lt;p align="left"&gt;0:008&gt; kc
 # 
00 ucrtbase!abort
01 VCRUNTIME140!_purecall
WARNING: Stack unwind information not available. Following frames may be wrong.
02 ClientTelemetry!Microsoft::Applications::Telemetry::LogManager::checkup
03 ClientTelemetry!Microsoft::Applications::Telemetry::EventProperty::type_name
04 ClientTelemetry!Microsoft::Applications::Telemetry::EventProperty::type_name
05 ClientTelemetry!Microsoft::Applications::Telemetry::EventProperty::type_name
06 ClientTelemetry!Microsoft::Applications::Telemetry::EventProperty::type_name
07 wininet!InternetIndicateStatus
08 wininet!CFsm::RunWorkItem
09 wininet!CSocket::ReceiveCompletion
0a wininet!CWxSocket::IoCompletionCallback
0b KERNELBASE!BasepTpIoCallback
0c ntdll!TppIopExecuteCallback
0d ntdll!TppWorkerThread
0e kernel32!BaseThreadInitThunk
0f ntdll!__RtlUserThreadStart
10 ntdll!_RtlUserThreadStart&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Some runtime implementations replace NULL code pointers with some default functions which provide additional diagnostics, for example, in the case of C++ pure virtual call:</p>
<p align="left">0:008> kc<br />
 #<br />
00 ucrtbase!abort<br />
01 VCRUNTIME140!_purecall<br />
WARNING: Stack unwind information not available. Following frames may be wrong.<br />
02 ClientTelemetry!Microsoft::Applications::Telemetry::LogManager::checkup<br />
03 ClientTelemetry!Microsoft::Applications::Telemetry::EventProperty::type_name<br />
04 ClientTelemetry!Microsoft::Applications::Telemetry::EventProperty::type_name<br />
05 ClientTelemetry!Microsoft::Applications::Telemetry::EventProperty::type_name<br />
06 ClientTelemetry!Microsoft::Applications::Telemetry::EventProperty::type_name<br />
07 wininet!InternetIndicateStatus<br />
08 wininet!CFsm::RunWorkItem<br />
09 wininet!CSocket::ReceiveCompletion<br />
0a wininet!CWxSocket::IoCompletionCallback<br />
0b KERNELBASE!BasepTpIoCallback<br />
0c ntdll!TppIopExecuteCallback<br />
0d ntdll!TppWorkerThread<br />
0e kernel32!BaseThreadInitThunk<br />
0f ntdll!__RtlUserThreadStart<br />
10 ntdll!_RtlUserThreadStart</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 9)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/#comment-137139</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 9)</dc:creator>
		<pubDate>Mon, 22 Mar 2010 20:54:55 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/#comment-137139</guid>
		<description>[...] Today we introduce an icon for NULL Pointer (code) pattern: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Today we introduce an icon for NULL Pointer (code) pattern: [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Hunting for a Driver</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/#comment-83185</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Hunting for a Driver</dc:creator>
		<pubDate>Mon, 06 Jul 2009 15:57:02 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/#comment-83185</guid>
		<description>[...] resulted effective address is a NULL code pointer (EAX=3, major code and ESI is [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] resulted effective address is a NULL code pointer (EAX=3, major code and ESI is [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Stack trace, invalid code pointer and hooked functions: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/#comment-74272</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Stack trace, invalid code pointer and hooked functions: pattern cooperation</dc:creator>
		<pubDate>Wed, 13 May 2009 13:50:17 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/#comment-74272</guid>
		<description>[...] looking at a stack trace of one crashed process we noticed an invalid code pointer. It is not a NULL code pointer but has the same stack trace [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] looking at a stack trace of one crashed process we noticed an invalid code pointer. It is not a NULL code pointer but has the same stack trace [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 6b)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/#comment-71305</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 6b)</dc:creator>
		<pubDate>Tue, 14 Apr 2009 17:51:03 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/#comment-71305</guid>
		<description>[...] Analysis NULL Data Pointer is a special version of the more general Invalid Pointer pattern like NULL Code Pointer. The effective address is below 0xFFFF and it is usually a register with 0 value and the small [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Analysis NULL Data Pointer is a special version of the more general Invalid Pointer pattern like NULL Code Pointer. The effective address is below 0xFFFF and it is usually a register with 0 value and the small [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; NULL code pointer, changed environment and hooked functions: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/#comment-64268</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; NULL code pointer, changed environment and hooked functions: pattern cooperation</dc:creator>
		<pubDate>Wed, 04 Feb 2009 17:11:40 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/04/28/crash-dump-analysis-patterns-part-6a/#comment-64268</guid>
		<description>[...] 2009 (0x7D9) - The Year of Debugging  2010 (0x7DA) - The Year of Dump Analysis It was reported that after an upgrade to the new version of a productivity software package one unrelated GUI application started to crash frequently. One crash dump was collected and the following stack trace pointed to a NULL code pointer: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 2009 (0&#215;7D9) - The Year of Debugging  2010 (0&#215;7DA) - The Year of Dump Analysis It was reported that after an upgrade to the new version of a productivity software package one unrelated GUI application started to crash frequently. One crash dump was collected and the following stack trace pointed to a NULL code pointer: [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
