Michael, It looks like the toolchain is configured as OSELAS.Toolchain-2014.12. I've recently been added to a team which had this existing ptxdist setup, so I've been trying to learn my way around ptxdist while trying to get valgrind enabled to test an issue.
The initial run of valgrind results in the message shown in my first message: > > ==5596== Memcheck, a memory error detector > ==5596== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. > ==5596== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright > info > ==5596== Command: /usr/bin/device > ==5596== > > 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: strcmp > valgrind: in an object with soname matching: ld-linux-armhf.so.3 > valgrind: was not found whilst processing > valgrind: symbols from the object with soname: ld-linux-armhf.so.3 > 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. The package you need > valgrind: to install for fix (1) is called > valgrind: > valgrind: On Debian, Ubuntu: libc6-dbg > valgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo > valgrind: > valgrind: Cannot continue -- exiting now. Sorry. Since ld-linux-armhf.so.3 is a symlink to ld-2.20.so, I copied ld-2.20.so from the root-debug/lib location and re-ran valgrind. The referenced function changed, but the file it expected it in did not (for brevity, I've only retained the function and file lines). > > ... > valgrind: A must-be-redirected function > valgrind: whose name matches the pattern: memcpy > valgrind: in an object with soname matching: ld-linux-armhf.so.3 > valgrind: was not found whilst processing > valgrind: symbols from the object with soname: ld-linux-armhf.so.3 > ... The fact that the reference was expected in the same file, along with additional searching, led me to think that the optimization was the problem. Thanks, - Jason -----Original Message----- From: ptxdist [mailto:ptxdist-boun...@pengutronix.de] On Behalf Of Michael Olbrich Sent: Tuesday, March 27, 2018 3:34 AM To: ptxdist@pengutronix.de Subject: Re: [ptxdist] Including valgrind in the configuration doesn't trigger an un-optimized build of glibc. Hi, On Mon, Mar 26, 2018 at 07:03:21AM -0500, Crim, Jason wrote: > 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. Hmm, strage, The only problems I've seen are with stripped binaries. Which toolchain are you using? 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
