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?

   > > Does someone still use mtrace when valgrind is better and
   > > faster?
   > And doesn't support most of the platforms glibc does.
   >>From valgrind homepage

   It runs on the following platforms: X86/Linux, AMD64/Linux,
   ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS32/Linux,
   MIPS64/Linux, ARM/Android (2.3.x and later), X86/Android (4.0 and
   later), X86/Darwin and AMD64/Darwin (Mac OS X 10.7, with limited
   support for 10.8).

   Please state which are platforms that are supported by glibc and
   improtant programs running only on that platform needs mtrace

>From the README:


	i[4567]86-*-linux-gnu, x86_64-*-linux-gnu,
	powerpc-*-linux-gnu, powerpc64*-*-linux-gnu, s390-*-linux-gnu,
	s390x-*-linux-gnu, sh[34]-*-linux-gnu, sparc*-*-linux-gnu,

	aarch64*-*-linux-gnu, alpha*-*-linux-gnu, am33*-*-linux-gnu,
	arm-*-linux-gnueabi, hppa-*-linux-gnu, ia64-*-linux-gnu,
	m68k-*-linux-gnu, mips-*-linux-gnu, mips64-*-linux-gnu,
	tilegx-*-linux-gnu, tilepro-*-linux-gnu

Then there is also *-k*bsd-gnu...

mtrace has its uses, it works, and people use is... Why deprecate a
useful tool?

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