http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55844
--- Comment #3 from Kostya Serebryany <kcc at gcc dot gnu.org> 2013-01-02 17:31:05 UTC --- >> we should just move over to using the dwarf unwinder and forget about the >> manually unwinding the stack Upstream asan-rt has two flags now: ---------- fast_unwind_on_fatal 1 Use Fast/Slow unwinder when found a bug. The fast one relies on frame pointers, while slow one does not. The default may change to 0 soon. fast_unwind_on_malloc 1 Same as fast_unwind_on_fatal, but control unwinding inside malloc/free, i.e. performance critical. ---------- I am going to switch the default for fast_unwind_on_fatal to 0 somewhere in Jan and then merge to gcc. fast_unwind_on_malloc will remain 1 by default; see the rationale in http://code.google.com/p/address-sanitizer/issues/detail?id=137#c6
