Comment #3 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
Although CrashReporter has some private API to add information to a
crashlog, that would only add additional information. The main stack trace
is still taken by CrashReporter itself, and tools that work with crash logs
will use this trace.
But I'm more surprised that LLDB is actually truncating the stack trace as
well, which makes debugging terrible, and that also makes this look like
something worth fixing in ASan itself.
It also seems to me that this could be done by forcing having a stackframe
in __asan_report_error only, by using the ENABLE_FRAME_POINTER macro, which
we're already using elsewhere (asan_mac.cc). What do you think?
--
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.
