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

2019-02-21 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #15 from Tom de Vries --- (In reply to Jakub Jelinek from comment #13) > You can try, but it seems upstream doesn't really care. Done: https://reviews.llvm.org/D58493

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

2019-02-21 Thread dennis.khalikov at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #14 from Denis Khalikov --- IMHO, this is a really hard to face in real word. You, probably, have to write your program on assembly and then let "as" to add section with debuginfo, because "as" can not generate dwarf tag

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

2019-02-21 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #13 from Jakub Jelinek --- You can try, but it seems upstream doesn't really care.

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

2019-02-21 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #12 from Tom de Vries --- (In reply to Tom de Vries from comment #11) > Created attachment 45652 [details] > Tentative patch > > Patch proposed in comment #10, added ChangeLog and rationale, bootstrapped > and reg-tested. Hi Jakub,

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

2019-02-10 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #11 from Tom de Vries --- Created attachment 45652 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45652=edit Tentative patch Patch proposed in comment #10, added ChangeLog and rationale, bootstrapped and reg-tested.

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

2019-02-10 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 Tom de Vries changed: What|Removed |Added CC||vries at gcc dot gnu.org --- Comment #10

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

2017-06-16 Thread d.khalikov at partner dot samsung.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #9 from Denis Khalikov --- I've added patch for review https://reviews.llvm.org/D34149

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

2017-06-13 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #8 from Jakub Jelinek --- (In reply to Denis Khalikov from comment #7) > Thanks, I was mistaken, fix should be in the libbacktrace. No, I wasn't saying that. I meant: static int SymbolizeCodePCInfoCallback(void *vdata, uintptr_t

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

2017-06-13 Thread d.khalikov at partner dot samsung.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #7 from Denis Khalikov --- Thanks, I was mistaken, fix should be in the libbacktrace.

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

2017-06-13 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #6 from Jakub Jelinek --- The thing is that for backtrace_pcinfo the callback can be called multiple times. And IMNSHO the hack you want to do (fill in file/line in the backtrace_pcinfo call and function during backtrace_syminfo) is

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

2017-06-13 Thread d.khalikov at partner dot samsung.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #5 from Denis Khalikov --- As I understood libbacktrace has two main calls to symbolize pc. 1. backtrace_pcinfo /* Given a PC, find the file name, line number, and function name. */ 164 165 int 166 backtrace_pcinfo (struct

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

2017-06-13 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #4 from Jakub Jelinek --- (In reply to Denis Khalikov from comment #3) > This fix > 111 AddressInfo *info = cdata->get_new_frame(addr); > 112 if (filename) > 113 info->file = internal_strdup(filename); > 114 info->line =

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

2017-06-13 Thread d.khalikov at partner dot samsung.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #3 from Denis Khalikov --- This fix 111 AddressInfo *info = cdata->get_new_frame(addr); 112 if (filename) 113 info->file = internal_strdup(filename); 114 info->line = lineno; 115 if (function) { 116 info->function =

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

2017-06-13 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 --- Comment #2 from Jakub Jelinek --- libbacktrace upstream is in GCC, and the libsanitizer libbacktrace support, while it is upstream, is not what LLVM uses (they have their own symbolizer instead, using external program).

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

2017-06-13 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81081 Richard Biener changed: What|Removed |Added Keywords||diagnostic