[Bug 1858794] Re: AddressSanitizer with LTO does not show file name and line number in backtrace

2020-01-08 Thread Abhay Sachan
** Description changed: Using ASan/UBSan with LTO leads to printing of only hex offsets in the stacktraces. The issue seems to be fixed in gcc-9 on Eoan, but it doesnt work with bionic gcc-8. There is a GCC bug for this, which was fixed an year ago, but it is not - there in bionin gcc-8

[Bug 1858794] Re: AddressSanitizer with LTO does not show file name and line number in backtrace

2020-01-08 Thread Abhay Sachan
** Description changed: Using ASan/UBSan with LTO leads to printing of only hex offsets in the stacktraces. The issue seems to be fixed in gcc-9 on Eoan, but it doesnt work with bionic gcc-8. There is a GCC bug for this, which was fixed an year ago, but it is not there in bionin gcc-8

[Bug 1858794] Re: AddressSanitizer with LTO does not show file name and line number in backtrace

2020-01-08 Thread Abhay Sachan
Eoan gcc-v output: gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.2.1-9ubuntu2' --w

[Bug 1858794] [NEW] AddressSanitizer with LTO does not show file name and line number in backtrace

2020-01-08 Thread Abhay Sachan
Public bug reported: Using ASan/UBSan with LTO leads to printing of only hex offsets in the stacktraces. The issue seems to be fixed in gcc-9 on Eoan, but it doesnt work with bionic gcc-8. There is a GCC bug for this, which was fixed an year ago, but it is not there in bionin gcc-8. https://gcc.