title: using catch(...) (ellipsis) for post-mortem analysis
body: <p>Someone in a different question suggested using <code>catch(...)</code> to capture all otherwise unhandled - unexpected/unforseen exceptions by surrounding the whole <code>main()</code> with the <code>try{}catch(...){}</code> block.</p>
  
  <p>It sounds like an interesting idea that could save a lot of time debugging the program and leave at least a hint of what happened.</p>
  
  <p>The essence of the question is <strong>what information can be recovered</strong> that way (other than whatever debug globals I leave behind), <strong>and how</strong> to recover it (how to access and recognize whatever catch was called with) </p>
  
  <p>Also, what caveats are connected with it. In particular:</p>
  
  <ul>
  <li>will it play nice with threads that sprout later?</li>
  <li>will it not break handling segfaults (captured elsewhere as signal)</li>
  <li>will it not affect other try...catch blocks inevitably nested inside, that are there to handle expected exceptions?</li>
  </ul>