From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26292 invoked by alias); 16 Nov 2016 01:37:08 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 26278 invoked by uid 89); 16 Nov 2016 01:37:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy= X-HELO: relay1.mentorg.com Date: Wed, 16 Nov 2016 01:37:00 -0000 From: Joseph Myers To: Florian Weimer CC: Subject: Re: [PATCH] malloc: Deprecate hook variables, __default_morecore, In-Reply-To: Message-ID: References: <20161026150218.3F1A4439942E0@oldenburg.str.redhat.com> <11f59117-e5a4-4c62-739c-e05e01ee43b3@redhat.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2016-11/txt/msg00522.txt.bz2 On Tue, 15 Nov 2016, Florian Weimer wrote: > > I don't consider valgrind suitable for replacing the uses of mtrace in the > > glibc testsuite (or other similar uses elsewhere for lightweight checking > > for leaks). > > I completely agree. > > The above is for the NEWS file, for external use. For internal use, we still > need a solution. (I have an mtrace-compatible interposition-based tracer > almost finished, but it may not make the cut for the next release, and it may > be superseded by DJ's work anyway.) I think we can run internal deprecation > at a different pace than external deprecation. Well, I think mtrace (meaning the ability to run with tracing then run the mtrace script to process the results, more than the functions to turn tracing on and off) is similarly useful externally as a lightweight system for tracing allocations and detecting leaks. And it is of course documented in the manual. -- Joseph S. Myers joseph@codesourcery.com