This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH BZ#20422] Do not allow asan/msan/tsan and fortify at the same time.
- From: Florian Weimer <fweimer at redhat dot com>
- To: Maxim Ostapenko <m dot ostapenko at samsung dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Cc: Kostya Serebryany <kcc at google dot com>, Yuri Gribov <tetra2005 at gmail dot com>
- Date: Tue, 6 Sep 2016 11:44:36 +0200
- Subject: Re: [PATCH BZ#20422] Do not allow asan/msan/tsan and fortify at the same time.
- Authentication-results: sourceware.org; auth=none
- References: <57CDAB08.email@example.com> <firstname.lastname@example.org> <57CE8965.email@example.com>
On 09/06/2016 11:16 AM, Maxim Ostapenko wrote:
At least for Memory Sanitizer, the documentation clearly says that
*everything* has to be compiled with it. I read that as as meaning
that the interceptors are just a kludge.
I thought we should compile everything except Glibc, no? Compiling Glibc
with MSan would be tricky, that's why it needs interceptors.
There are some parts of glibc which cannot be instrumented, like most
things involved early in process startup. But there is nothing really
special about, say, getpwuid, or even strerror.