Thanks, I'd tried moving over the root-debug versions of the referenced files, and was still hitting the error. That's when I'd found the post referencing the optimization levels. I'll take a look at getting the nfs-root running when I've got some time.
Thanks for the information and advice, - Jason -----Original Message----- From: ptxdist [mailto:ptxdist-boun...@pengutronix.de] On Behalf Of Michael Olbrich Sent: Monday, March 26, 2018 2:30 AM To: ptxdist@pengutronix.de Subject: Re: [ptxdist] Including valgrind in the configuration doesn't trigger an un-optimized build of glibc. Hi, On Thu, Mar 22, 2018 at 12:38:21PM -0500, Crim, Jason wrote: > I'm currently using ptxdist 2015.10.0 and I've selected valgrind as a > built-in option in the 'Debug Tools' using menuconfig. Valgrind is > then installed in my image at /usr/bin/valgrind. However, it is > currently not usable since the available glibc is too optimized, > resulting in the following message. [...] > Is there a method of configuring glibc to build un-optimized ( below > -O2) for use with the valgrind tool? > > Can the valgrind selection automatically trigger this un-optimized > build? > > Or, if there are other suggestions for addressing this issue, I'd like > to hear them. The problem is not the optimization, but the missing debug symbols. With this PTXdist Version you need to use the nfsroot. The debug symbols are available there. Or you can update to the latest PTXdist and Toolchain version. Then you can enable debug packages that can be installed on the live system. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de
