Displaying 1 result from an estimated 1 matches for "__asan_report_error".
Did you mean:
__asan_report_error_2
2014 Aug 27
2
[LLVMdev] Verifying unwind info/debugging a crash in _Unwind_Backtrace() on OSX
...ompiler-rt/lib/sanitizer_common/sanitizer_unwind.cc:116
I've inserted a debug printf into the callback passed to
_Unwind_Backtrace (note the "got pc" lines above) and can see that
_Unwind_Backtrace correctly finds the address of the function that
calls SlowUnwindStack (it's named __asan_report_error), but then
crashes.
Is there a way to check whether the unwind info is correct? Could this
be a bug in the system implementation of _Unwind_Backtrace, which
probably should not crash in the middle of a valid stack trace?
Thanks in advance for any pointers,
Alexander Potapenko
PS. LMK if this is...