diff options
| author | Vitaly Buka <vitalybuka@google.com> | 2017-08-01 21:15:19 +0000 |
|---|---|---|
| committer | Vitaly Buka <vitalybuka@google.com> | 2017-08-01 21:15:19 +0000 |
| commit | d4e03d59cb23b9639096264acf8e973589b4f5ad (patch) | |
| tree | 750e457f955ce408c882fb54231452f6295c0c03 /llvm/lib/ProfileData/Coverage/CoverageMapping.cpp | |
| parent | eacf4e408bb6f82affa5186b38409c6bda751059 (diff) | |
| download | llvm-d4e03d59cb23b9639096264acf8e973589b4f5ad.zip llvm-d4e03d59cb23b9639096264acf8e973589b4f5ad.tar.gz llvm-d4e03d59cb23b9639096264acf8e973589b4f5ad.tar.bz2 | |
[sanitizer_common] Fuchsia support for interceptors
Summary:
Actually Fuchsia non-support for interceptors. Fuchsia doesn't use
interceptors in the common sense at all. Almost all system library
functions don't need interception at all, because the system
libraries are just themselves compiled with sanitizers enabled and
have specific hook interfaces where needed to inform the sanitizer
runtime about thread lifetimes and the like. For the few functions
that do get intercepted, they don't use a generic mechanism like
dlsym with RTLD_NEXT to find the underlying system library function.
Instead, they use specific extra symbol names published by the
system library (e.g. __unsanitized_memcpy).
Submitted on behalf of Roland McGrath.
Reviewers: vitalybuka, alekseyshl, kcc, filcab
Reviewed By: filcab
Subscribers: kubamracek, phosek, filcab, llvm-commits
Tags: #sanitizers
Differential Revision: https://reviews.llvm.org/D36028
llvm-svn: 309745
Diffstat (limited to 'llvm/lib/ProfileData/Coverage/CoverageMapping.cpp')
0 files changed, 0 insertions, 0 deletions