[RFC] Deprecating mtrace?

Alfred M. Szmidt ams@gnu.org
Mon Nov 4 00:24:00 GMT 2013


The usage cases between valgrind and mtrace are so vastly different
that which is better is a matter of what you are doing, there several
cases when valgrind simply cannot do the job.  For example,
enabling/disabling leak tracing on a already running process, or when
you are only interested in parts of the code where you might suspect a
leak in a long running process, or enable tracing automatically when
you hit some trigger (e.g. memory usage exceeding some limit).  Two
different tools, with two different goals, mtrace for programmatically
doing traces, and valgrind for interactive usage.



More information about the Libc-alpha mailing list