Yes, it would be handy. I find that almost all use cases for that are covered by either sleep_before_dying, or just running the entire things under a debugger from the start, but sometimes I wish we had this feature.
On Wed Oct 29 2014 at 10:46:36 AM Alexander Potapenko < ramosian.gli...@gmail.com> wrote: > Someone did consider it, but I think it just wasn't important enough. > Doesn't the sleep_before_dying option work for you? > On Oct 29, 2014 12:24 AM, "Yury Gribov" <y.gri...@samsung.com> wrote: > >> Hi all, >> >> Has anyone considered adding a flag to ASAN_OPTIONS to start gdb >> automatically when __asan_report* is called? Might be handy sometimes. >> >> -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. > -- 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.
