On Thu, Aug 26, 2010 at 2:34 PM, Sorin Dumitru <sdumi...@ixiacom.com> wrote: > I am running into a little problem using valgrind 3.5 on powerpc. When I > start valgrind with --leak-check=full I get some warnings at the start: > > --247-- WARNING: Serious error when reading debug info > --247-- When reading debug info > from /shared/chassis/arch/lib/valgrind/vgpreload_core-ppc32-linux.so: > --247-- Can't make sense of .sdata section mapping > [ ... ] > > This does not happen when I use version 3.3. Did anything change between > those two versions that might explain this? > > The full output from valgrind can be found here: > http://pastebin.com/YwPQV0wA
Some PPC compilers generate debug info by default in the stabs format. It's possible that something has changed in Valgrind with regard to reading stabs debug info between version 3.3 and 3.5. The quickest way to get useful output from Valgrind 3.5.0 or later on PowerPC is to build Valgrind and the applications that you want to analyze with DWARF debug information (gcc command-line option -gdwarf-2; specify CFLAGS=-gdwarf-2 when configuring Valgrind). Bart. ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
