On Tue, Jun 10, 2014 at 12:10 PM, Yuri Gribov <tetra2...@gmail.com> 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). Being able to fix more than one error at once would > significantly reduce debugging time.
Sometimes -- yes. But there are downsides: one bug may trigger another report and the user will spend time investigating more reports than needed. > >> It will create more problems to users and developers than it will solve. > > Agreed, it may cause false positives, duplicated reports, etc. But it > does not have to be enabled by default. These, and many more. Next time, someone will request suppressions. I remain unconvinced... > > -Y > > -- > You received this message because you are subscribed to the Google Groups > "address-sanitizer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to address-sanitizer+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to address-sanitizer+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
