<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bug on ZeroSharp</title><link>https://www.zerosharp.com/blog/categories/bug/</link><description>Recent content in Bug on ZeroSharp</description><generator>Hugo</generator><language>en-gb</language><copyright>Copyright © 2012–{year} Robert Anderson</copyright><lastBuildDate>Mon, 29 Apr 2013 16:21:00 +0100</lastBuildDate><atom:link href="https://www.zerosharp.com/blog/categories/bug/index.xml" rel="self" type="application/rss+xml"/><item><title>Fixing an unmanaged code AppCrash</title><link>https://www.zerosharp.com/fixing-an-unmanaged-code-appcrash/</link><pubDate>Mon, 29 Apr 2013 16:21:00 +0100</pubDate><guid>https://www.zerosharp.com/fixing-an-unmanaged-code-appcrash/</guid><description>&lt;p&gt;This post is the result of a recent bug hunt in which I came across a tricky bug, found a debugging switch I&amp;rsquo;d completely forgotten existed and learned a little about calling &lt;code&gt;extern&lt;/code&gt; string functions from C#.&lt;/p&gt;
&lt;p&gt;I love bug hunting. It&amp;rsquo;s like a murder mystery: you&amp;rsquo;ve got your suspects and you try to eliminate them one at a time until, as a famous bug hunter said:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;hellip; when you have eliminated the impossible, whatever remains, however improbable, must be the truth.&lt;/p&gt;</description></item></channel></rss>