Re: Future of -fsanitize-recover

2014-06-10 Thread 'Alexey Samsonov' via address-sanitizer
On Tue, Jun 10, 2014 at 3:42 AM, 'Evgeniy Stepanov' via address-sanitizer < address-sanitizer@googlegroups.com> wrote: > On Tue, Jun 10, 2014 at 1:26 PM, Konstantin Serebryany > wrote: > > On Tue, Jun 10, 2014 at 12:50 PM, Yuri Gribov > wrote: > >>> there are downsides: one bug may trigger anoth

Re: Future of -fsanitize-recover

2014-06-10 Thread 'Evgeniy Stepanov' via address-sanitizer
On Tue, Jun 10, 2014 at 1:26 PM, Konstantin Serebryany wrote: > On Tue, Jun 10, 2014 at 12:50 PM, Yuri Gribov wrote: >>> there are downsides: one bug may trigger another report >> >> Doesn't UBSan have the same problem? > > Maybe, but ubsan reports totally different kinds of bugs. > Note that I a

Re: Future of -fsanitize-recover

2014-06-10 Thread Konstantin Serebryany
On Tue, Jun 10, 2014 at 12:50 PM, Yuri Gribov wrote: >> there are downsides: one bug may trigger another report > > Doesn't UBSan have the same problem? Maybe, but ubsan reports totally different kinds of bugs. Note that I am not opposed to -fsanitize-recover in tsan and msan (it's there already)

Re: Future of -fsanitize-recover

2014-06-10 Thread Yuri Gribov
> there are downsides: one bug may trigger another report Doesn't UBSan have the same problem? > the user will spend time investigating more reports than needed. True but that would be a concious trade-off. >>> It will create more problems to users and developers than it will solve. >> >> Agree

Re: Future of -fsanitize-recover

2014-06-10 Thread Konstantin Serebryany
On Tue, Jun 10, 2014 at 12:10 PM, Yuri Gribov wrote: >> What are your reasons? > > Collect more memory errors from a single run. E.g. I have an > "embedded" system at hand which requires at least 20m for typical > fix-compile-run cycle (and some steps like reflashing the device are > manual). Bein

Re: Future of -fsanitize-recover

2014-06-10 Thread Yuri Gribov
> What are your reasons? Collect more memory errors from a single run. E.g. I have an "embedded" system at hand which requires at least 20m for typical fix-compile-run cycle (and some steps like reflashing the device are manual). Being able to fix more than one error at once would significantly re

Re: Future of -fsanitize-recover

2014-06-10 Thread Konstantin Serebryany
On Tue, Jun 10, 2014 at 11:56 AM, Yuri Gribov wrote: > All, > > Are there plans to extend -fsanitize-recover beyond UBSan? It seems > that adding this functionality to e.g. ASan would be trivial. I do not plan to add such functionality to asan and I am strongly opposed to it. It will create more

Future of -fsanitize-recover

2014-06-10 Thread Yuri Gribov
All, Are there plans to extend -fsanitize-recover beyond UBSan? It seems that adding this functionality to e.g. ASan would be trivial. -Y -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving em