Displaying 13 results from an estimated 13 matches for "__asan_init".
2014 Oct 23
3
[LLVMdev] compiler-rt with MSVC 2013
...>> /FORCE:multiple to work around that, but then any usage of free()
>> within compiler-rt is liable to find the asan definition.
>
> I don't know, it just worked :)
LoL, not a vote of confidence. ;-)
>
>>> I'm not 100% sure off the top of my head but I think __asan_init is
>>> explicitly called from the CRT init code later than calloc gets
>>> called() from CRT. To handle everything correctly, calloc() must be
>>> "statically" intercepted before __asan_init is called from the CRT
>>> (hence before "dynamic"...
2016 May 25
4
Runtime interception: design problem
...ect should be developped under the
correct directory but I don't see how this should be designed in order that
the code optimized by BoundsCheking Pass uses my own malloc&free functions.
I spent quite some time on Asan runtime code and found that runtime could
be initialized with a call to __asan_init() (function defined in
asan_rtl.cc) from the instrumented code directly but I don't know if it's
the only way to do it or how to reproduce it...
So to resume, I want to make my own malloc and free function to be called
by the code I instrument with BoundsChecking. Any suggestion is welcome...
2014 Oct 23
2
[LLVMdev] compiler-rt with MSVC 2013
...of free()
>>>> within compiler-rt is liable to find the asan definition.
>>>
>>> I don't know, it just worked :)
>>
>> LoL, not a vote of confidence. ;-)
>>
>>>
>>>>> I'm not 100% sure off the top of my head but I think __asan_init is
>>>>> explicitly called from the CRT init code later than calloc gets
>>>>> called() from CRT. To handle everything correctly, calloc() must be
>>>>> "statically" intercepted before __asan_init is called from the CRT
>>>>> (h...
2014 Oct 23
2
[LLVMdev] compiler-rt with MSVC 2013
...he linker finds the duplicate definition of
any of those functions, it will produce that link error. You can use
/FORCE:multiple to work around that, but then any usage of free()
within compiler-rt is liable to find the asan definition.
> I'm not 100% sure off the top of my head but I think __asan_init is
> explicitly called from the CRT init code later than calloc gets
> called() from CRT. To handle everything correctly, calloc() must be
> "statically" intercepted before __asan_init is called from the CRT
> (hence before "dynamic" interceptors are set up).
>
&...
2016 May 26
0
Runtime interception: design problem
...be developped under the correct directory but I don't see how this should be designed in order that the code optimized by BoundsCheking Pass uses my own malloc&free functions.
>
> I spent quite some time on Asan runtime code and found that runtime could be initialized with a call to __asan_init() (function defined in asan_rtl.cc) from the instrumented code directly but I don't know if it's the only way to do it or how to reproduce it...
>
> So to resume, I want to make my own malloc and free function to be called by the code I instrument with BoundsChecking. Any suggestion...
2014 Oct 23
2
[LLVMdev] compiler-rt with MSVC 2013
...to find the asan definition.
>>>>>
>>>>> I don't know, it just worked :)
>>>>
>>>> LoL, not a vote of confidence. ;-)
>>>>
>>>>>
>>>>>>> I'm not 100% sure off the top of my head but I think __asan_init is
>>>>>>> explicitly called from the CRT init code later than calloc gets
>>>>>>> called() from CRT. To handle everything correctly, calloc() must be
>>>>>>> "statically" intercepted before __asan_init is called from the CRT...
2014 Oct 23
2
[LLVMdev] compiler-rt with MSVC 2013
I think this issue is that we were not using the INTERCEPTOR macros to
define these functions. The following patch seems to work for me to
get the build linking again, however, I cannot test -- when I run
check-asan, I get:
2> lit.py: lit.common.cfg:59: fatal: Invalid llvm_tools_dir config
attribute: 'E:/llvm/2013/$(Configuration)/bin'
~Aaron
On Thu, Oct 23, 2014 at 1:20 PM, Aaron
2014 Jan 15
4
[LLVMdev] [PATCH] Removing -fsanitize-address-zero-base-shadow
Hi,
we plan to remove -fsanitize-address-zero-base-shadow command line
flag from clang, and disable zero-base shadow support on all platforms
where it is not the default behavior.
- It is completely unused, as far as we know. And completely undocumented, too.
- It is ABI-incompatible with non-zero-base shadow, which means all
objects in a process must be built with the same setting. Failing to
2020 Jun 24
7
RFC: Sanitizer-based Heap Profiler
...tack alloc context id is found, a new entry is
created. If this causes an eviction, the evicted entry is dumped
immediately (by default to stderr, otherwise to a specified report file).
Later post processing can merge dumped entries with the same stack alloc
context id.
Initialization
For ASAN, an __asan_init function initializes the memory allocation
tracking support, and the ASAN instrumentation pass in LLVM creates a
global constructor to invoke it. The heap profiler prototype adds a new
__heapprof_init function, which performs heap profile specific
initialization, and the heap profile instrumentatio...
2016 May 25
0
Runtime interception: design problem
...gt; the correct directory but I don't see how this should be designed in
> order that the code optimized by BoundsCheking Pass uses my own
> malloc&free functions.
>
> I spent quite some time on Asan runtime code and found that runtime
> could be initialized with a call to __asan_init() (function defined in
> asan_rtl.cc) from the instrumented code directly but I don't know if
> it's the only way to do it or how to reproduce it...
>
> So to resume, I want to make my own malloc and free function to be
> called by the code I instrument with BoundsChecking...
2020 Jul 05
2
RFC: Sanitizer-based Heap Profiler
...> is created. If this causes an eviction, the evicted entry is dumped
> immediately (by default to stderr, otherwise to a specified report file).
> Later post processing can merge dumped entries with the same stack alloc
> context id.
> Initialization
>
>
>
> For ASAN, an __asan_init function initializes the memory allocation
> tracking support, and the ASAN instrumentation pass in LLVM creates a
> global constructor to invoke it. The heap profiler prototype adds a new
> __heapprof_init function, which performs heap profile specific
> initialization, and the heap pr...
2020 Jun 25
1
RFC: Sanitizer-based Heap Profiler
...d. If this causes an eviction, the evicted entry is
> dumped immediately (by default to stderr, otherwise to a specified
> report file). Later post processing can merge dumped entries with the
> same stack alloc context id.
>
>
> Initialization
>
>
> For ASAN, an __asan_init function initializes the memory allocation
> tracking support, and the ASAN instrumentation pass in LLVM creates a
> global constructor to invoke it. The heap profiler prototype adds a
> new __heapprof_init function, which performs heap profile specific
> initialization, and the hea...
2020 Jul 09
2
RFC: Sanitizer-based Heap Profiler
...d. If this causes an eviction, the evicted entry is dumped
>> immediately (by default to stderr, otherwise to a specified report file).
>> Later post processing can merge dumped entries with the same stack alloc
>> context id.
>> Initialization
>>
>> For ASAN, an __asan_init function initializes the memory allocation
>> tracking support, and the ASAN instrumentation pass in LLVM creates a
>> global constructor to invoke it. The heap profiler prototype adds a new
>> __heapprof_init function, which performs heap profile specific
>> initialization,...