This is the mail archive of the 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?

On Sun, Nov 03, 2013 at 02:46:30PM -0500, Alfred M. Szmidt wrote:
> mtrace has its uses, it works, and people use is... Why deprecate a
> useful tool?

To know if something is deprecated you do not ask a question if it is
useful but a question if there is alternative that is better in most

You could on base of usefullness argue that you can ride a horse
as useful way of transport so people should learn riding a horse.

As finding leaks with valgrind is easier as it shows full backtrace,
does not show false positives like mtrace does and identified illegal
memory access you wasted time by learning mtrace when you should learn
valgrind anyway.

Also to part it work, to quote ulrich:

"mcheck does not work for multi-threaded code. It cannot possibly do.
There is no way to fix this with the technology underlying mcheck."

which speaks for itself as one can write a standalone portable leak
detector that is faster, supports multithreading and does not need
modification of binary in weekend.

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