From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH] malloc: Deprecate hook variables, __default_morecore, <mcheck.h>
Date: Wed, 16 Nov 2016 01:37:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611160134530.2244@digraph.polyomino.org.uk> (raw)
In-Reply-To: <bea209cf-2ba3-8414-478c-5d643907341e@redhat.com>
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
next prev parent reply other threads:[~2016-11-16 1:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 15:02 Florian Weimer
2016-10-26 15:55 ` Joseph Myers
2016-11-15 13:22 ` Florian Weimer
2016-11-15 15:39 ` Joseph Myers
2016-11-15 15:56 ` Florian Weimer
2016-11-16 1:37 ` Joseph Myers [this message]
2016-11-16 9:46 ` Will Newton
2016-11-17 13:00 ` Florian Weimer
2016-11-17 14:27 ` Joseph Myers
2016-11-17 14:50 ` Steve Vormwald
2016-11-17 16:08 ` Adhemerval Zanella
2016-11-18 9:13 ` Florian Weimer
2016-11-18 17:29 ` Steve Vormwald
2016-11-21 19:43 ` DJ Delorie
2016-11-22 15:12 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1611160134530.2244@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).