patch: break into debugger on death in sanitizers
chandlerc at google.com
Fri Oct 25 08:26:05 PDT 2013
Sigtrap, which seems less likely to cause deep surprise in the presence of
On Oct 25, 2013 3:56 AM, "Kostya Serebryany" <kcc at google.com> wrote:
> So this will change the default behavior from doing exit(1) to doing
> abort(), right?
> On Fri, Oct 25, 2013 at 3:16 AM, Nick Lewycky <nlewycky at google.com> wrote:
>> 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.
>> Add a trap to the exit path in sanitizer_common. Please review!
>> cfe-commits mailing list
>> cfe-commits at cs.uiuc.edu
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-commits