|
From: Alessandro B. <a.b...@ev...> - 2010-07-21 16:06:06
|
Some more informations: this is the output of valgrind running with my example program. ==611== Memcheck, a memory error detector ==611== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==611== Using Valgrind-3.6.0.SVN and LibVEX; rerun with -h for copyright info ==611== Command: ../../pcc_test ==611== --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 mtrace test1 ==611== Use of uninitialised value of size 4 ==611== at 0xFE7B288: _itoa_word (_itoa.c:196) ==611== by 0xFE7ECC7: vfprintf@@GLIBC_2.4 (vfprintf.c:1579) ==611== by 0xFE86203: printf@@GLIBC_2.4 (printf.c:35) ==611== by 0x100005FF: ??? (in /home/valgrind/pcc_test) ==611== by 0xFE4D703: (below main) (libc-start.c:222) ==611== ==611== Conditional jump or move depends on uninitialised value(s) ==611== at 0xFE7B290: _itoa_word (_itoa.c:196) ==611== by 0xFE7ECC7: vfprintf@@GLIBC_2.4 (vfprintf.c:1579) ==611== by 0xFE86203: printf@@GLIBC_2.4 (printf.c:35) ==611== by 0x100005FF: ??? (in /home/valgrind/pcc_test) ==611== by 0xFE4D703: (below main) (libc-start.c:222) ==611== ==611== Conditional jump or move depends on uninitialised value(s) ==611== at 0xFE7DF04: vfprintf@@GLIBC_2.4 (vfprintf.c:1579) ==611== by 0xFE86203: printf@@GLIBC_2.4 (printf.c:35) ==611== by 0x100005FF: ??? (in /home/valgrind/pcc_test) ==611== by 0xFE4D703: (below main) (libc-start.c:222) ==611== ==611== Conditional jump or move depends on uninitialised value(s) ==611== at 0xFE7DF5C: vfprintf@@GLIBC_2.4 (vfprintf.c:1579) ==611== by 0xFE86203: printf@@GLIBC_2.4 (printf.c:35) ==611== by 0x100005FF: ??? (in /home/valgrind/pcc_test) ==611== by 0xFE4D703: (below main) (libc-start.c:222) ==611== 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 000000000000000000000000000000 ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== Warning: invalid file descriptor -1 in syscall close() ==611== ==611== HEAP SUMMARY: ==611== in use at exit: 0 bytes in 0 blocks ==611== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==611== ==611== All heap blocks were freed -- no leaks are possible ==611== ==611== For counts of detected and suppressed errors, rerun with: -v ==611== Use --track-origins=yes to see where uninitialised values come from ==611== ERROR SUMMARY: 788 errors from 4 contexts (suppressed: 5 from 3) The list of 00000000000000000000000000000000 is the output of the program :) Thanks. Il giorno mer, 21/07/2010 alle 14.48 +0200, Alessandro Biasci 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 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 > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |