On Fri, Oct 25, 2013 at 11:52 AM, Kostya Serebryany <[email protected]> wrote:
> I am not opposed to this change, but I'd like to test it a bit more > carefully to make sure none of our users get angry on us for behavior > change. > I'd suggest to put this sigtrap under a flag (off by default) and then > flip the default to true after a bit of testing. > We already have abort_on_error, may add sigtrap_on_error or some such. > Ugh. So, I'm kind of sad about this because this is the number one most frustrating part of debugging UBSan and ASan failures -- they completely misbehave when running under gdb. =[
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
