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 <[email protected]> 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! > > Nick > > _______________________________________________ > cfe-commits mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits > >
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
