This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.25 seems to have broken AddressSaniitzer Inbox x glibc x sanitizer x
- From: Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, Szabolcs Nagy <szabolcs dot nagy at arm dot com>, Florian Weimer <fweimer at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, nd at arm dot com
- Date: Tue, 08 May 2018 21:59:51 +0000
- Subject: Re: glibc 2.25 seems to have broken AddressSaniitzer Inbox x glibc x sanitizer x
- References: <CAGQ9bdyZDj6gs6G3h2gQ2UyWVMHpuYi3SU0zyJKfGDumP3hJTA@mail.gmail.com> <bb5bec42-3dad-b064-4c74-ed54a96a7149@linaro.org> <bef28268-a86b-d573-185b-146b2f6a78c5@redhat.com> <a30bf9e8-cbea-66c2-d051-2ad31aae3c9d@redhat.com> <7f3d146c-7b91-c362-fb2f-561a08c7d239@redhat.com> <c9a6f035-6212-8b85-b0ea-85e3d92ad805@linaro.org> <980b324f-e8ff-4886-763c-dd8f29a94ede@redhat.com> <2748d850-3b28-b8da-4ad4-126c1253dbe2@arm.com> <4c4eb7e6-c683-639e-04dd-898687154fba@linaro.org> <596a3496-462d-2b56-0680-2e3d67de3e63@redhat.com> <CAGQ9bdxhhYk4vRCV47sA7_y=b-xE+Rgf+LegjvdH-Tv9bqiEsg@mail.gmail.com>
up.
Any chance we can get better glibc<=>asan cross testing and collaboration?
Today users are complaining about glibc 2.27 and -m32:
https://github.com/google/sanitizers/issues/954
Thanks
--kcc
On Thu, Mar 1, 2018 at 11:26 AM Konstantin Serebryany <
konstantin.s.serebryany@gmail.com> wrote:
> > In fact I consider a heinous crime for ASAN to have not
> > reached out to all C library vendors they interface with
> We did reach glibc, more than four years ago now, didn't we?
> For at least one other libc (Android's bionic) we have much less
> hackish integration.
> The OSX/iOS integration is in Apple's hands, and I haven't heard
> complaints there.
> > to get an API to do what they want. Hacks like this come
> > back to bit all of us, and then we disappoint users and
> > take several cycles to fix things instead of having
> > implemented them correctly up front.
> >
> > We are not blameless though. We are like the slowest project
> > in the world :-)
> >
> > --
> > Cheers,
> > Carlos.