On (04/01/12 04:39), McClintock Matthew-B29882 wrote: > On Tue, Jan 3, 2012 at 10:31 PM, Garg Vakul-B16394 <b16...@freescale.com> > wrote: > > Hi Matthew > > > > I am not sure if I understood your point fully. > > > > I am suggesting to do below mentioned as suggested on valgrind page. > > http://valgrind.org/docs/manual/dist.readme-packagers.html > > > > > > "If you don't want to leave symbols on ld.so, alternatively you can have > > your distro install ld.so's debuginfo package by default, or make > > ld.so.debuginfo be a requirement of your Valgrind RPM/DEB/whatever." > > This is what I am suggest. If we include valgrind in an image and the > arch is powerpc or powerpc64, we need to include ld.so with debug > symbols by default. Otherwise valgrind will not work at all. This > seems like a reasonable thing to do for these two arches.
I think we might be evading the real issue here. Which symbols are valgrind interested in ? is this something ppc specific or general case. Are we stripping ld.so too much ? some of the symbols are needed to be kept for ld.so for gdb to work and I am guessing its similar kind of issue here. If you can figure this then we may solve this issue by just not stripping needed symbols _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
