title: Debug setting improper signal handler
body: <p>I've got an odd issue with Visual Studio 2013 (using 2012 CTP toolset). When an assertion fails, the error message is printed and then the program exits without the debugger breaking, so all the debug information is lost. So far I've used <code>atexit</code>, <code>set_terminate</code>, and <code>signal(SIGABRT, ...)</code> to break, but none have any success. Since I know that <code>abort()</code> is called and <code>abort</code> raises <code>SIGABRT</code> then it seems to me like somebody must have overridden my <code>SIGABRT</code> handler.</p>
  
  <p>How can I catch where this occurs? I want to, say, break when somebody calls <code>signal(SIGABRT,...)</code>. </p>