SO:
$ uname -r
2.6.25.7-alcore
Toolchain:
$ ./powerpc-angstrom-linux-gcc -v
Using built-in specs.
Target: powerpc-angstrom-linux
Configured
with:
/disk2/build/native-sonnet/build/work/i686-ppc8xx-sdk-angstrom-linux/gcc-cross-sdk-4.1.1-r3/gcc-4.1.1/configure
--build=i686-linux --host=i686-linux --target=powerpc-angstrom-linux
--prefix=/usr/local/angstrom/powerpc
--exec_prefix=/usr/local/angstrom/powerpc
--bindir=/usr/local/angstrom/powerpc/bin
--sbindir=/usr/local/angstrom/powerpc/bin
--libexecdir=/usr/local/angstrom/powerpc/libexec
--datadir=/usr/local/angstrom/powerpc/share
--sysconfdir=/usr/local/angstrom/powerpc/etc
--sharedstatedir=/usr/local/angstrom/powerpc/share/com
--localstatedir=/usr/local/angstrom/powerpc/var
--libdir=/usr/local/angstrom/powerpc/lib
--includedir=/usr/local/angstrom/powerpc/include
--oldincludedir=/usr/local/angstrom/powerpc/include
--infodir=/usr/local/angstrom/powerpc/share/info
--mandir=/usr/local/angstrom/powerpc/share/man --with-gnu-ld
--enable-shared --enable-target-optspace --enable-languages=c,c++
--enable-threads=posix --enable-multilib --enable-c99 --enable-long-long
--enable-symvers=gnu --enable-libstdcxx-pch
--program-prefix=powerpc-angstrom-linux-
--with-local-prefix=/disk2/build/native-sonnet/build/staging/powerpc-angstrom-linux/usr
--with-gxx-include-dir=/disk2/build/native-sonnet/build/staging/powerpc-angstrom-linux//usr/include/c++
--with-sysroot=/usr/local/angstrom/powerpc/powerpc-angstrom-linux
--with-build-sysroot=/disk2/build/native-sonnet/build/staging/powerpc-angstrom-linux
--with-float=soft --enable-__cxa_atexit
Thread model: posix
gcc version 4.1.1
Valgrind for ls -l:
$ ./valgrind ls -l
==1471== Memcheck, a memory error detector
==1471== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==1471== Using Valgrind-3.6.0.SVN and LibVEX; rerun with -h for
copyright info
==1471== Command: ls -l
==1471==
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.
I don't have the non stripped version of glibc for this platform. I try
to get different libraries and valgrind start (but the sistem became
unstable).
Il giorno gio, 22/07/2010 alle 10.00 -0700, John Mehaffey ha scritto:
>
>
> On Thu, Jul 22, 2010 at 12:06 AM, Alessandro Biasci
> <[email protected]> wrote:
> Yes this is output from console of my board. Instead, this is
> the output
> of Valgrind on initialization for debug my program:
>
> --611-- WARNING: Serious error when reading debug info
> --611-- When reading debug info from /home/valgrind/pcc_test:
> --611-- Can't make sense of .sdata section mapping
> --611-- WARNING: Serious error when reading debug info
> --611-- When reading debug info
> from
> /home/valgrind/ppcInstall/lib/valgrind/vgpreload_core-ppc32-linux.so:
> --611-- Can't make sense of .sdata section mapping
> --611-- WARNING: Serious error when reading debug info
> --611-- When reading debug info
> from
> /home/valgrind/ppcInstall/lib/valgrind/vgpreload_memcheck-ppc32-linux.so:
> --611-- Can't make sense of .sdata section mapping
>
> Valgrind seems not working well on my system but I don't know
> why :(
>
> Some help??
>
> You don't say what your operating system is, nor what tools you used
> to
> compile your application.
>
> You might try running valgrind on a simple command, such as "ls" (on
> Linux),
> to see if it has any issues.
>
> You might try compiling your app with gcc, if you are not using it
> already, with
> the "-g" flag.
>
> I suspect that the errors valgrind are finding are real, but it is
> limited as to
> the information it can give back in stack traces due to the warnings
> at the
> beginning.
>
> HTH!
> -mehaf
>
>
> Il giorno mer, 21/07/2010 alle 16.34 -0700, John Mehaffey ha
> scritto:
>
> > >
> > > Hi, I'm trying to run Valgrind on PowerPC (mpc885) but I
> have some
> > > problems.
> > >
> > > When I start valgrind I received this message:
> > >
> > > [ 741.302816] Bad emulation memcheck-ppc32-/987
> > > [ 741.302925] NIP: 38030e28 instruction: 10000484
> opcode: 4 A: 0 B: 0
> > > C: 12 code: 242 rc: 0
> > > [ 741.310302] pte @ 0x38030e28:
> > > (0xc39b1380)->(0xc39630c0)->0x02efe889
> > > [ 741.310302] RPN: 02efe PP: 2 SPS: 1 SH: 0 CI: 0 v: 1
> > > [ 741.310302] Kernel VA for NIP c2efee28 pte @
> 0xc2efee28: no pmd
> > >
> > These don't look like messages from Valgrind. Is this from
> the
> > system console?
> >
> > The opcode 0x10000484 is the prototypical Altivec
> instruction
> > (vor 0,0,0) that Valgrind uses to check if your system
> supports
> > Altivec instructions.
> >
> > Most likely you can ignore this, Valgrind is expecting
> either
> > a SIGILL (or not), and should get the SIGILL in this case.
> >
> > -mehaf
> > > These are the steps for compile it:
> > >
> > > svn co
> svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_5_BRANCH
> > > . /usr/local/angstrom/powerpc/environment-setup
> > > ./autogen.sh
> > > ./configure
> --prefix=/home/alessandro/Siemens/Valgrind/ppc_install
> > > --host=powerpc-angstrom-linux --enable-only32bit
> --disable-tls
> > >
> > > Modify the line:
> > > in m_transtab.c
> > > vg_assert(cls == 16 || cls == 32 || cls == 64 || cls
> == 128);
> > > in m_machine.c
> > > vg_assert(szB == 16 || szB == 32 || szB == 64 || szB
> == 128);
> > > in guest_ppc_toIR.c
> > > vassert(lineszB == 16 || lineszB == 32 || lineszB ==
> 64 || lineszB ==
> > > 128);
> > >
> > >
> > > make
> > > make install
> > >
> > > I have also try to run a program but no memory leak was
> found (there
> > > were instead).
> > >
> > > Some Help ??
> > >
> >
> >
> >
> >
>
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first --
> http://p.sf.net/sfu/sprint-com-first
> > _______________________________________________
> > Valgrind-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
>
>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
