title: Continue to debug after failed assertion on Linux?
body: <p>When an assertion fails with Visual C++ on Windows, the debugger stops, displays the message, and then lets you continue (or, if no debugging session is running, offers to launch visual studio for you).</p>
  
  <p>On Linux, it seems that the default behavior of assert() is to display the error and quit the program. Since all my asserts go through macros, I tried to use signals to get around this problem, like</p>
  
  <pre><code>#define ASSERT(TEST) if(!(TEST)) raise(SIGSTOP);
  </code></pre>
  
  <p>But although <a href="http://en.wikipedia.org/wiki/GNU_Debugger" rel="nofollow noreferrer">GDB</a> (through <a href="http://en.wikipedia.org/wiki/KDevelop" rel="nofollow noreferrer">KDevelop</a>) stops at the correct point, I can't seem to continue past the signal, and sending the signal manually within GDB just leaves me hanging, with control of neither GDB nor the debugged process. </p>