This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: glibc 2.26 memory leak with MySQL?
- From: DJ Delorie <dj at redhat dot com>
- To: brunni at netestate dot de
- Cc: "Carlos O'Donell" <carlos at redhat dot com>, libc-help at sourceware dot org
- Date: Thu, 24 Aug 2017 10:56:24 -0400
- Subject: Re: glibc 2.26 memory leak with MySQL?
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=dj at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com B349340430A
"Carlos O'Donell" <carlos@redhat.com> writes:
> DJ,
>
> Do we have a rebased tracer against glibc 2.26?
I've built a rawhide-based tracer (with F26 builds as well) and put the
details and patches here:
http://people.redhat.com/dj/glibc/
Once a trace is captured and converted into a workload, it can be
simulated on a range of platforms to see how they affect malloc
performance, or inspected to try to analyze it.
DJ