title: Can I put try / catch around an OS API that crashes?
body: <p>I use a Windows OS library to manipulate image files.  Sometimes it crashes deep inside it for no apparent reason—all the inputs are reasonable and its not a threading issue.  The crash is memory A/V.</p>
  
  <p>So, what are the down sides to something like this:</p>
  
  <pre><code>try {
    pFoo = OsAPIThatCrashes();
  } catch {
    pFoo = NULL;
  }
  </code></pre>
  
  <p>Will that even work?  We don't use exceptions anywhere else in our code.</p>