<p dir="ltr">Sigtrap, which seems less likely to cause deep surprise in the presence of signal handlers.</p>
<div class="gmail_quote">On Oct 25, 2013 3:56 AM, "Kostya Serebryany" <<a href="mailto:kcc@google.com">kcc@google.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">So this will change the default behavior from doing exit(1) to doing abort(), right? </div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 25, 2013 at 3:16 AM, Nick Lewycky <span dir="ltr"><<a href="mailto:nlewycky@google.com" target="_blank">nlewycky@google.com</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Running sanitized code under gdb can be annoying because the program will print out its error then exit, instead of the usual behaviour when we get an abort() of stopping the program there and allowing the user to inspect its stack trace.<div>



<br></div><div>Add a trap to the exit path in sanitizer_common. Please review!</div><span><font color="#888888"><div><br></div><div>Nick</div></font></span></div>
<br>_______________________________________________<br>
cfe-commits mailing list<br>
<a href="mailto:cfe-commits@cs.uiuc.edu" target="_blank">cfe-commits@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
cfe-commits mailing list<br>
<a href="mailto:cfe-commits@cs.uiuc.edu">cfe-commits@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits</a><br>
<br></blockquote></div>