Bug 78878 - stacktrace engine can't use compressed/separated debug info for extracting symbols.
Summary: stacktrace engine can't use compressed/separated debug info for extracting sy...
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: sanitizer (show other bugs)
Version: 6.2.1
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-21 09:32 UTC by Pawel Sikora
Modified: 2018-11-23 10:54 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2018-11-23 00:00:00


Attachments
testcase (23.37 KB, application/x-gtar-compressed)
2016-12-21 09:32 UTC, Pawel Sikora
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pawel Sikora 2016-12-21 09:32:22 UTC
Created attachment 40384 [details]
testcase

hi,

i've noticed that compressed debuginfo (or externally accessible via .gnu_debuglink section) is not used for decorating sanitizer stacktrace.


e.g.:

=================================================================
==6290==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 4 byte(s) in 1 object(s) allocated from:
    #0 0x7f4d243840ce in operator new(unsigned long) (/lib64/liblsan.so.0+0xe0ce)
    #1 0x400693  (/home/pawels/bugs/mem-leak/m+0x400693)
    #2 0x40069f  (/home/pawels/bugs/mem-leak/m+0x40069f)
    #3 0x7f4d23728400 in __libc_start_main (/lib64/libc.so.6+0x20400)


without compression/debuglink the stacktrace is more readable:

=================================================================
==6318==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 4 byte(s) in 1 object(s) allocated from:
    #0 0x7efe533370ce in operator new(unsigned long) (/lib64/liblsan.so.0+0xe0ce)
    #1 0x400693 in leak() /home/pawels/bugs/mem-leak/m.cpp:4
    #2 0x40069f in main /home/pawels/bugs/mem-leak/m.cpp:8
    #3 0x7efe526db400 in __libc_start_main (/lib64/libc.so.6+0x20400)
Comment 1 Martin Liška 2018-11-23 09:39:49 UTC
Maxim, what's the status of the support?
Comment 3 Martin Liška 2018-11-23 10:54:48 UTC
Great, then let's close it.