[ELDK] Recent valgrind on libc 2.6, ELDK 4.2 (ppc_4xx) ?
Detlev Zundel
dzu at denx.de
Wed Mar 17 16:49:26 CET 2010
Hi Charles,
> I found it impossible to compile a recent version of valgrind because
> of unsupported/unrecognized assembler commands using the DENX ELDK
> 4.2/ppc_4xx toolchain.
Can you give more details on why this fails? I was under the impression
that this should work pretty flawlessly, but I haven;t checked lately.
> A fellow coworker pointed me to
> ftp://ftp.denx.de/pub/tmp/valgrind-2.4.1-ppc.tar.gz which compiles and
> works (once you remove the glibc version check from the configure
> script). At this point, valgrind works on our target, but it keeps
> reporting "Conditional jump or move depends on uninitialised value(s)"
> error within libstdc++. Also, it doesn't seem to follow memory
> allocation using the c++ 'new' operator. I haven't gone more in depth
> with that version, because it seems it wasn't made to work with glibc
> 2.6 (the configure script checked for 2.1, 2.2, 2.3, or 2.4), and
> because it's an old version of valgrind.
I agree. You should concentrate on getting a recent version to work.
So maybe if you show us more details on what fails, we can help.
Cheers
Detlev
--
2) interrupt handler runs a long time: I'm sure we still have some of those
especially in the archaelogical corners of drivers/* and in the creative space
of the embedded "oh, I don't know why but it works" departement. That's code
which needs to be fixed anyway. -- Thomas Gleixner
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
More information about the eldk
mailing list