search for: capturestackbacktrace

Hi David, Eric, LLVM devs, You've probably heard about AddressSanitizer (ASan) and other sanitizers based on LLVM. One of the things that makes ASan not as awesome on Windows as it is on Linux is the symbolization of the stacks. Currently, ASan runtime on Windows uses CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 to unwind and symbolize stacks. This works like a charm in-process for stack frames built with CL, but yields "function+0x0ff537" for frames built with Clang. I came up with a prototype which emits "old-style debug info" COFF sections that are...

Martin, good to hear from you. Thanks for the effort - I will test on 32bit and 64bit Windows 10. I will report ASAP. Ivan On Sun, Aug 16, 2020 at 8:42 PM Martin Storsjö <martin at martin.st> wrote: > On Sat, 15 Aug 2020, Ivan Serdyuk wrote: > > > > > > > On Sat, Aug 15, 2020 at 8:39 PM Martin Storsjö <martin at martin.st> wrote: > > Hi, > >

...c, LLVM devs, > > You've probably heard about AddressSanitizer (ASan) and other > sanitizers based on LLVM. One of the things that makes ASan > not as awesome on Windows as it is on Linux > is the symbolization of the stacks. > > Currently, ASan runtime on Windows uses > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 > to unwind and symbolize stacks. This works like a charm > in-process for stack frames built with CL, but yields > "function+0x0ff537" for frames built with Clang. > > I came up with a prototype which emits "old-style debug info"...

...9;ve probably heard about AddressSanitizer (ASan) and other > > sanitizers based on LLVM. One of the things that makes ASan > > not as awesome on Windows as it is on Linux > > is the symbolization of the stacks. > > > > Currently, ASan runtime on Windows uses > > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 > > to unwind and symbolize stacks. This works like a charm > > in-process for stack frames built with CL, but yields > > "function+0x0ff537" for frames built with Clang. > > > > I came up with a prototype which emits "o...

...t AddressSanitizer (ASan) and other >> > sanitizers based on LLVM. One of the things that makes ASan >> > not as awesome on Windows as it is on Linux >> > is the symbolization of the stacks. >> > >> > Currently, ASan runtime on Windows uses >> > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 >> > to unwind and symbolize stacks. This works like a charm >> > in-process for stack frames built with CL, but yields >> > "function+0x0ff537" for frames built with Clang. >> > >> > I came up with a prototype...

...t;>>>> > not as awesome on Windows as it is on Linux >> >>>>>> > is the symbolization of the stacks. >> >>>>>> > >> >>>>>> > Currently, ASan runtime on Windows uses >> >>>>>> > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 >> >>>>>> > to unwind and symbolize stacks. This works like a charm >> >>>>>> > in-process for stack frames built with CL, but yields >> >>>>>> > "function+0x0ff537" for fram...

...) and other >>> > sanitizers based on LLVM. One of the things that makes ASan >>> > not as awesome on Windows as it is on Linux >>> > is the symbolization of the stacks. >>> > >>> > Currently, ASan runtime on Windows uses >>> > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 >>> > to unwind and symbolize stacks. This works like a charm >>> > in-process for stack frames built with CL, but yields >>> > "function+0x0ff537" for frames built with Clang. >>> > >>> > I came...

...gt; not as awesome on Windows as it is on Linux > >> >>>>>> > is the symbolization of the stacks. > >> >>>>>> > > >> >>>>>> > Currently, ASan runtime on Windows uses > >> >>>>>> > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 > >> >>>>>> > to unwind and symbolize stacks. This works like a charm > >> >>>>>> > in-process for stack frames built with CL, but yields > >> >>>>>> > "function+0x0ff537...

...me on Windows as it is on Linux >> >> >>>>>> > is the symbolization of the stacks. >> >> >>>>>> > >> >> >>>>>> > Currently, ASan runtime on Windows uses >> >> >>>>>> > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 >> >> >>>>>> > to unwind and symbolize stacks. This works like a charm >> >> >>>>>> > in-process for stack frames built with CL, but yields >> >> >>>>>> > "funct...

...of the things that makes ASan >>>>>> > not as awesome on Windows as it is on Linux >>>>>> > is the symbolization of the stacks. >>>>>> > >>>>>> > Currently, ASan runtime on Windows uses >>>>>> > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 >>>>>> > to unwind and symbolize stacks. This works like a charm >>>>>> > in-process for stack frames built with CL, but yields >>>>>> > "function+0x0ff537" for frames built with Clang. >&g...

...ASan > >>>>>> > not as awesome on Windows as it is on Linux > >>>>>> > is the symbolization of the stacks. > >>>>>> > > >>>>>> > Currently, ASan runtime on Windows uses > >>>>>> > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 > >>>>>> > to unwind and symbolize stacks. This works like a charm > >>>>>> > in-process for stack frames built with CL, but yields > >>>>>> > "function+0x0ff537" for frames built wit...

...> > sanitizers based on LLVM. One of the things that makes ASan >>>> > not as awesome on Windows as it is on Linux >>>> > is the symbolization of the stacks. >>>> > >>>> > Currently, ASan runtime on Windows uses >>>> > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 >>>> > to unwind and symbolize stacks. This works like a charm >>>> > in-process for stack frames built with CL, but yields >>>> > "function+0x0ff537" for frames built with Clang. >>>> > >>...

...based on LLVM. One of the things that makes ASan >>>>> > not as awesome on Windows as it is on Linux >>>>> > is the symbolization of the stacks. >>>>> > >>>>> > Currently, ASan runtime on Windows uses >>>>> > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 >>>>> > to unwind and symbolize stacks. This works like a charm >>>>> > in-process for stack frames built with CL, but yields >>>>> > "function+0x0ff537" for frames built with Clang. >>>>&g...

...t AddressSanitizer (ASan) and other >> > sanitizers based on LLVM. One of the things that makes ASan >> > not as awesome on Windows as it is on Linux >> > is the symbolization of the stacks. >> > >> > Currently, ASan runtime on Windows uses >> > CaptureStackBackTrace/SymFromAddr/SymGetLineFromAddr64 >> > to unwind and symbolize stacks. This works like a charm >> > in-process for stack frames built with CL, but yields >> > "function+0x0ff537" for frames built with Clang. >> > >> > I came up with a prototype...