[Bug sanitizer/81081] [ASAN] ASAN is not properly calling libbacktrace to symbolize program written on assembler

rguenth at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Tue Jun 13 10:47:00 GMT 2017


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2017-06-13
                 CC|                            |rguenth at gcc dot gnu.org
             Blocks|                            |78063
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I've also seen this behavior (throwing away useful data) with PR78063.  So
fixing this would also help PR78063 for the cases ASAN backtraces are affected
(I needed to adjust the testsuite outcome for early LTO debug).

Confirmed.

Not sure if this is part of upstream asan (so should be reported there) or if
this is part of GCC local changes.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78063
[Bug 78063] libbacktrace fails to handle cross CU DW_AT_abstract_origin


More information about the Gcc-bugs mailing list