[ELDK] ELDK issue with Valgrind

[Robert Berger]

Eric/Detelev,

>On 06/08/2010 01:00 PM, eldk-request at lists.denx.de wrote:
>Message: 4 Date: Mon, 7 Jun 2010 17:58:39 -0400 From: Eric Millbrandt
><emillbrandt at dekaresearch.com> Subject: Re: [ELDK] ELDK issue with
>Valgrind........ To: 'Detlev Zundel' <dzu at denx.de> Cc:
>"eldk at lists.denx.de" <eldk at lists.denx.de> Message-ID:
><0A40042D85E7C84DB443060EC44B3FD3253ECB8C80 at dekaexchange07.deka.local>
>Content-Type: text/plain; charset="us-ascii"
>> > What I do not understand - and what I do not see in the bug report
>- is
>> > how you got hold of the debug symbols for the ELDK rootfile
>system.  Can
>> > you please update me on this important detail?
>> >
>> > Thanks
>> >   Detlev
>> >
>Hi Detlev,
>
>Install the glibc-debuginfo rpm for your architecture from one of the
>eldk mirrors,
http://mira.sunsite.utk.edu/eldk/4.2/ppc-linux->x86>/debug/ .  Valgrind
knows how to read symbols from the detached symbol >file.
>
Eric/Detlev,

I just managed to build/install today's version of the valgrind trunk on
my kilauea board with eldk 4.2

Now I have the infamous problem:
valgrind:  Fatal error at startup: a function redirection
valgrind:  which is mandatory for this platform-tool combination
valgrind:  cannot be set up.  Details of the redirection are:
valgrind:
valgrind:  A must-be-redirected function
valgrind:  whose name matches the pattern:      strlen
valgrind:  in an object with soname matching:   ld.so.1
valgrind:  was not found whilst processing
valgrind:  symbols from the object with soname: ld.so.1
valgrind:
valgrind:  Possible fixes: (1, short term): install glibc's debuginfo
valgrind:  package on this machine.  (2, longer term): ask the packagers
valgrind:  for your Linux distribution to please in future ship a non-
valgrind:  stripped ld.so (or whatever the dynamic linker .so is called)
valgrind:  that exports the above-named function using the standard
valgrind:  calling conventions for this platform.
valgrind:
valgrind:  Cannot continue -- exiting now.  Sorry.

Before I'll try to rebuild the glibc in order to get a non stripped
ld.so I tried to do what Eric suggested.

${CROSS_COMPILE}rpm -i glib-debuginfo-ppc_4xx-1.2.10-26.ppc.rpm
${CROSS_COMPILE}rpm -i glib2-debuginfo-ppc_4xx-2.12.13-1.ppc.rpm

... but unfortunately without success.

Do I need to uninstall something before?
Eric, which rpm fixed the problem for you?

Can you please advise?

Regards,

Robert

-- 
Robert Berger
Embedded Software Specialist

Reliable Embedded Systems
Consulting Training Engineering
Tel.: (+30) 697 593 3428
Fax.:(+30) 210 684 7881
email: robert.berger at reliableembeddedsystems.com
URL: http://www.reliableembeddedsystems.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
..."It is NOT portable (uses 386 task switching etc), and it probably
never will support anything other than AT-harddisks, as that's all I
have :-(." - Linus Benedict Torvalds(torvalds at klaava.Helsinki.FI),
1991-08-25 23:12:08 PST -

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1