<?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 70)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2008/07/10/crash-dump-analysis-patterns-part-70/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 10:24:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 96)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/07/10/crash-dump-analysis-patterns-part-70/#comment-126939</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Crash Dump Analysis Patterns (Part 96)</dc:creator>
		<pubDate>Sun, 21 Feb 2010 23:56:40 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/07/10/crash-dump-analysis-patterns-part-70/#comment-126939</guid>
		<description>[...] we disassemble it we see an inlined string or memory copy, perhaps wcscpy [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we disassemble it we see an inlined string or memory copy, perhaps wcscpy [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; NULL data pointer, stack trace, inline function optimization and platformorphic fault: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2008/07/10/crash-dump-analysis-patterns-part-70/#comment-86247</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; NULL data pointer, stack trace, inline function optimization and platformorphic fault: pattern cooperation</dc:creator>
		<pubDate>Mon, 27 Jul 2009 20:05:28 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2008/07/10/crash-dump-analysis-patterns-part-70/#comment-86247</guid>
		<description>[...] We also don&#8217;t see memcpy call but if we look at the faulted instruction we suspect it was inlined memcpy [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] We also don&#8217;t see memcpy call but if we look at the faulted instruction we suspect it was inlined memcpy [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
