|
From: Soenmez, F. <fah...@hb...> - 2008-06-05 10:24:35
|
Hi all, on our PowerPC we start our software with valgrind. This is our system/target: CPU: MPC5200B OS: Elinos glibc 2.3.4 Our approach: 1.) STRIP=/opt/elinos-4.0/cdk/ppc/60x/glibc-2.3.4/bin/ppc_60x-strip CC=/opt/elinos-4.0/cdk/ppc/60x/glibc-2.3.4/bin/ppc_60x-gcc LD=/opt/elinos-4.0/cdk/ppc/60x/glibc-2.3.4/bin/ppc_60x-g++ CXX=/opt/elinos-4.0/cdk/ppc/60x/glibc-2.3.4/bin/ppc_60x-g++ AR=/opt/elinos-4.0/cdk/ppc/60x/glibc-2.3.4/bin/ppc_60x-ar BUILD_CC=/opt/elinos-4.0/cdk/ppc/60x/glibc-2.3.4/bin/ppc_60x-gcc BUILD_LD=/opt/elinos-4.0/cdk/ppc/60x/glibc-2.3.4/bin/ppc_60x-g++ BUILD_CXX=/opt/elinos-4.0/cdk/ppc/60x/glibc-2.3.4/bin/ppc_60x-g++ BUILD_AR=/opt/elinos-4.0/cdk/ppc/60x/glibc-2.3.4/bin/ppc_60x-ar BUILD_LDXX=/opt/elinos-4.0/cdk/ppc/60x/glibc-2.3.4/bin/ppc_60x-g++ ./configure --host=powerpc-pcc-linux --disable-tls --enable-only32bit --without-x 2.) make 3.) We copy the file valgrid and memcheck in our target and run Valgrind write this message: -> valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': No such file or directory Does anybody have an idea how it can be avoided that the vargrinf run? What do you suggest to get an acceptable result? Kind regards & thank you Fahri Hottinger Baldwin Messtechnik GmbH, Im Tiefen See 45, 64293 Darmstadt, Germany | www.hbm.com Registered as GmbH (German limited liability corporation) in the commercial register at the local court of Darmstadt, HRB 1147 Company domiciled in Darmstadt | CEO: Andreas Huellhorst | Chairman of the board: James Charles Webster Als Gesellschaft mit beschraenkter Haftung eingetragen im Handelsregister des Amtsgerichts Darmstadt unter HRB 1147 Sitz der Gesellschaft: Darmstadt | Geschaeftsfuehrung: Andreas Huellhorst | Aufsichtsratsvorsitzender: James Charles Webster The information in this email is confidential. It is intended solely for the addressee. If you are not the intended recipient, please let me know and delete this email. Die in dieser E-Mail enthaltene Information ist vertraulich und lediglich fur den Empfaenger bestimmt. Sollten Sie nicht der eigentliche Empfaenger sein, informieren Sie mich bitte kurz und loeschen diese E-Mail. |
|
From: Bart V. A. <bar...@gm...> - 2008-06-05 10:38:03
|
On Thu, Jun 5, 2008 at 12:24 PM, Soenmez, Fahri <fah...@hb...> wrote: > -> valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': > No such file or directory This is because you did not copy all Valgrind files. If I remember correctly, when I last cross-compiled Valgrind for PPC I copied Valgrind as follows from build system to target: * run make install on the build system. * copy $PREFIX/bin/valgrind and the entire directory $PREFIX/lib/valgrind from the build system to the target system. Bart. |
|
From: Bart V. A. <bar...@gm...> - 2008-06-06 06:16:26
|
On Thu, Jun 5, 2008 at 5:07 PM, Soenmez, Fahri <fah...@hb...> wrote: > Thank you, the note was very helpful. > > I compile with the prefix="/" and valgrind work. > > next problem bad ELF magic number: > ... > valgrind: /bin/myAppl: bad ELF magic number > valgrind: /bin/myAppl: cannot execute binary file Does Valgrind print the same error for /bin/ls as for your application on the target system ? Bart. |
|
From: Bart V. A. <bar...@gm...> - 2008-06-06 06:44:46
|
On Fri, Jun 6, 2008 at 8:29 AM, Soenmez, Fahri <fah...@hb...> wrote: > yes, the same error! Which are the values of the macro's ELFMAG and SELFMAG, macro's which are defined in the header file <elf.h> included by your *cross*-compiler ? These macro's should have the following values: $ grep -nwE 'ELFMAG|SELFMAG' /usr/include/elf.h 121:#define ELFMAG "\177ELF" 122:#define SELFMAG 4 Bart. |