<?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 61b)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2014/11/15/crash-dump-analysis-patterns-part-61b/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Wed, 06 May 2026 09:46:25 +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/2014/11/15/crash-dump-analysis-patterns-part-61b/#comment-741717</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Mon, 19 Sep 2016 12:10:02 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2014/11/15/crash-dump-analysis-patterns-part-61b/#comment-741717</guid>
		<description>Enabling application verifier in gflags.exe to catch handle close stack traces may also reveal who closed the handle originally before we get the second invalid handle close. Use !htrace command there.</description>
		<content:encoded><![CDATA[<p>Enabling application verifier in gflags.exe to catch handle close stack traces may also reveal who closed the handle originally before we get the second invalid handle close. Use !htrace command there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
