Comment #7 on issue 375 by [email protected]: On OS X, stacktraces are
broken after a report is printed
https://code.google.com/p/address-sanitizer/issues/detail?id=375
CrashReporter and backtrace() currently unwind via eh_frame and/or stack
frames. That works fine for most code, including system libraries, because
on OS X system libraries (usually) don't use -fomit-frame-pointer. LLDB
does know how to use the compact unwind info, but apparently for i386 there
is a separate bug in LLDB, which I filed as rdar://problem/19570035.
Anyway, if it's okay, I'm going to submit the proposed workaround that
forces a proper stack frame on __asan_report_error
(http://reviews.llvm.org/D7103).
--
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.
