This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Deprecating mtrace?


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]