<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Diagnostics on Hermit Blog</title><link>https://hermit.no/tags/diagnostics/</link><description>Recent content in Diagnostics on Hermit Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 08 Jan 2018 11:47:11 +0100</lastBuildDate><atom:link href="https://hermit.no/tags/diagnostics/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing userdumps using IFIX</title><link>https://hermit.no/archive/2018-01-08-managing-userdumps-using-ifix/</link><pubDate>Mon, 08 Jan 2018 11:47:11 +0100</pubDate><guid>https://hermit.no/archive/2018-01-08-managing-userdumps-using-ifix/</guid><description>&lt;p&gt;User dumps are powerful diagnostics you can enable when an application crashes, and in particular when you see no obvious reason for it to crash.&lt;/p&gt;&#10;&lt;p&gt;In my case I have been struggling with Visual Studio crashes, and have been reporting these back to Microsoft.  The devs there love user dumps, because they show the exact state of the application when it crashed.   A user dump can be opened in a debugger, to reveal call stacks and lot of other useful information.&lt;/p&gt;</description></item></channel></rss>