Displaying 14 results from an estimated 14 matches for "symgetlinefromaddr64".
2011 Oct 06
2
[LLVMdev] [Patch] Build failure on Windows+MinGW (GCC and Clang)
...PI SymGetSymFromAddr64(HANDLE hProcess,DWORD64
qwAddr,PDWORD64 pdwDisplacement,PIMAGEHLP_SYMBOL64 Symbol);
^
In file included from M:\Development\Source\LLVM\lib\Support\Signals.cpp:33:
M:\Development\Source\LLVM\lib\Support/Windows/Signals.inc:129:31: error:
redefinition of 'SymGetLineFromAddr64' as different kind of symbol
static fpSymGetLineFromAddr64 SymGetLineFromAddr64;
^
M:/Development/mingw64/bin/../lib/clang/3.0/../../../x86_64-w64-mingw32/include\psdk_inc/_dbg_common.h:777:20:
note: previous definition is here
WINBOOL IMAGEAPI SymGetLineFromAddr...
2013 Nov 14
2
[LLVMdev] Adding line table debug information to LLVM on Windows
...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 sufficient to get function name /...
2013 Nov 15
0
[LLVMdev] Adding line table debug information to LLVM on Windows
...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 suff...
2013 Nov 15
2
[LLVMdev] Adding line table debug information to LLVM on Windows
...anitizer (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
&g...
2013 Nov 18
2
[LLVMdev] Adding line table debug information to LLVM on Windows
...r
>> > 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 debu...
2013 Dec 03
2
[LLVMdev] Adding line table debug information to LLVM on Windows
...some 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.
>> >...
2013 Nov 19
0
[LLVMdev] Adding line table debug information to LLVM on Windows
...tizers 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...
2013 Dec 03
0
[LLVMdev] Adding line table debug information to LLVM on Windows
...t 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 Clan...
2013 Dec 03
1
[LLVMdev] Adding line table debug information to LLVM on Windows
...t;> >> >>>>>> > 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 bui...
2013 Nov 20
2
[LLVMdev] Adding line table debug information to LLVM on Windows
...>>>>> > 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.
>>>>>> >
>>&...
2013 Dec 03
0
[LLVMdev] Adding line table debug information to LLVM on Windows
...> 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.
> >>>>>...
2013 Nov 19
6
[LLVMdev] Adding line table debug information to LLVM on Windows
.... 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 pr...
2013 Nov 20
0
[LLVMdev] Adding line table debug information to LLVM on Windows
...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.
>>>>> >
>>>>> >...
2013 Nov 20
0
[LLVMdev] unsubscribe
...r
>> > 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 debu...