Displaying 3 results from an estimated 3 matches for "initializecallbacks".
2018 Feb 22
2
Memory sanitizer porting
...ions of CodeGenModule::isInSanitizerBlacklist function).
What happens is that for some reason memory sanitizer:
— still tries to partially instrument the blacklisted code;
— does not check whether its global memory storage variables are already defined.
The second issue, present in MemorySanitizer::initializeCallbacks, adds a second copy of storage global variables when compiling msan.cc (e.g. __emutls_v.__msan_retval_tls.63, __emutls_v.__msan_param_tls.65), and this results in an undefined reference during the linkage.
Here the question is what was initially intended to be done. I know that compiling blacklist...
2018 Feb 22
0
Memory sanitizer porting
...InSanitizerBlacklist function).
> What happens is that for some reason memory sanitizer:
> — still tries to partially instrument the blacklisted code;
> — does not check whether its global memory storage variables are already
> defined.
> The second issue, present in MemorySanitizer::initializeCallbacks, adds a
> second copy of storage global variables when compiling msan.cc (e.g.
> __emutls_v.__msan_retval_tls.63, __emutls_v.__msan_param_tls.65), and this
> results in an undefined reference during the linkage.
>
> Here the question is what was initially intended to be done. I know...
2018 Feb 25
1
Memory sanitizer porting
...function).
>> What happens is that for some reason memory sanitizer:
>> — still tries to partially instrument the blacklisted code;
>> — does not check whether its global memory storage variables are already
>> defined.
>> The second issue, present in MemorySanitizer::initializeCallbacks, adds a
>> second copy of storage global variables when compiling msan.cc (e.g.
>> __emutls_v.__msan_retval_tls.63, __emutls_v.__msan_param_tls.65), and this
>> results in an undefined reference during the linkage.
>>
>> Here the question is what was initially intende...