Comment #2 on issue 333 by [email protected]: Incomplete ASAN trace for
heap use-after-free on a temporary
http://code.google.com/p/address-sanitizer/issues/detail?id=333
FYI Asan uses something called "fast unwinder" to collect stack traces for
memory allocations. Fast unwinder has to be, well, fast so relies on frame
pointer which is not always available on most platforms so it may (and does
on x64 and ARM) lack precision unless you recompile all your code with
-fno-omit-frame-pointer. Another option would be running with
ASAN_OPTIONS=fast_unwind_on_malloc=0 but that would incur bigger perf
penalties. Setting fast_unwind_on_malloc=1 by default is a long debate but
Asan team prefers it to be that way.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
