This is the mail archive of the
mailing list for the glibc project.
Re: [RFC] Simple checking allocator
- From: OndÅej BÃlka <neleai at seznam dot cz>
- To: Petr Machata <pmachata at redhat dot com>
- Cc: Andi Kleen <andi at firstfloor dot org>, libc-alpha at sourceware dot org
- Date: Wed, 13 Nov 2013 10:43:08 +0100
- Subject: Re: [RFC] Simple checking allocator
- Authentication-results: sourceware.org; auth=none
- References: <20131021193617 dot GA29829 at domone dot podge> <20131021212655 dot GA32168 at domone dot podge> <20131022113959 dot GA7515 at domone dot podge> <8738nstl06 dot fsf at tassilo dot jf dot intel dot com> <20131023095158 dot GB6795 at domone dot podge> <m27gcchcra dot fsf at redhat dot com>
On Wed, Nov 13, 2013 at 10:28:09AM +0100, Petr Machata wrote:
> OndÅej BÃlka <email@example.com> writes:
> > On Wed, Oct 23, 2013 at 02:05:45AM -0700, Andi Kleen wrote:
> >> OndÅej BÃlka <firstname.lastname@example.org> writes:
> >> >
> >> > Comments?
> >> Better to just rely on valgrind or AddressSanitizer? Those
> >> will be always better for this.
> > Could if you accept a slowdown.
> Doesn't ElectrictFence do pretty much the same thing without slowdown.
No unless you have a program with only a few allocations.
It uses a mmap for each 16 byte allocation which is quite slow and
memory overhead of it is huge.