This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [patch] malloc per-thread cache ready for review
- From: Steve Vormwald <sdvormwa at cray dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Thu, 2 Feb 2017 20:00:10 +0000
- Subject: Re: [patch] malloc per-thread cache ready for review
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=sdvormwa at cray dot com;
- References: <AM5PR0802MB2610AFD1CCE5F168594E122C834C0@AM5PR0802MB2610.eurprd08.prod.outlook.com> (message from Wilco Dijkstra on Thu, 2 Feb 2017 19:03:50 +0000),<xn37fwl6pe.fsf@greed.delorie.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Is it possible to get traces from statically linked executables, assuming they are linked against the dj/malloc libc and I somehow arrange for tracing to be enabled early enough (eg, via a preinit_array function)? Or does this only work with dynamically linked executables?
Steven Vormwald