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?


On Sun, Nov 03, 2013 at 11:27:23AM -0800, pinskia@gmail.com wrote:
> 
> 
> > On Nov 3, 2013, at 11:17 AM, OndÅej BÃlka <neleai@seznam.cz> wrote:
> > 
> >> On Sun, Nov 03, 2013 at 07:01:07PM +0000, Joseph S. Myers wrote:
> >>> On Sun, 3 Nov 2013, Ondrej Bilka wrote:
> >>> 
> >>> Hi,
> >>> 
> >>> 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
> 
> AARCH64 is one which is important that is not currently supported by valgrind
> 
by the way did you tried a boehm-gc as a leak checker for aarch64?


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