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.gnu.org/bugzilla/show_bug.cgi?id=78063 I have attached a simple test program to demonstrate the problem: With bionic, gcc-8 gives: Direct leak of 4 byte(s) in 1 object(s) allocated from: #0 0x7f35f6106f00 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:86 #1 0x56193a9fb7f6 in leak (/home/asachan/leak+0x7f6) #2 0x56193a9fb812 in main (/home/asachan/leak+0x812) #3 0x7f35f5c49b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) With Eoan, gcc-9 gives: Direct leak of 4 byte(s) in 1 object(s) allocated from: #0 0x7fb3baa7eae8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dae8) #1 0x55c775c2e16a in leak /home/asachan/kachra/leak.c:7 #2 0x55c775c2e186 in main /home/asachan/kachra/leak.c:13 #3 0x7fb3ba7a71e2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x271e2) The fix seems to be in libbacktrace, which gets picked up in libsanitizer as well: https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=268663 ** Affects: gcc-8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Test program to reproduce the reported issue" https://bugs.launchpad.net/bugs/1858794/+attachment/5318566/+files/leak.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858794 Title: AddressSanitizer with LTO does not show file name and line number in backtrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-8/+bug/1858794/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
