* [Buildroot] valgrind issues on 2014.11-git buildroot @ 2014-12-04 6:57 Rohit Kumar 2014-12-04 13:50 ` Mike Williams 0 siblings, 1 reply; 5+ messages in thread From: Rohit Kumar @ 2014-12-04 6:57 UTC (permalink / raw) To: buildroot Hello, i am trying to build valgrind into my file system using buildroot. it compiles without problem. but when i try to run valgrind it throws me following error: ==174== Memcheck, a memory error detector ==174== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==174== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==174== Command: ./uart /dev/ttyS1 ==174== 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. is there any problem in configuration? configuration file is attached kindly help With Regards, Rohit Kumar +82 1073149173 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141204/ead6da3f/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: .config Type: application/octet-stream Size: 56907 bytes Desc: not available URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141204/ead6da3f/attachment.obj> ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] valgrind issues on 2014.11-git buildroot 2014-12-04 6:57 [Buildroot] valgrind issues on 2014.11-git buildroot Rohit Kumar @ 2014-12-04 13:50 ` Mike Williams 2014-12-04 15:26 ` Rohit Kumar 0 siblings, 1 reply; 5+ messages in thread From: Mike Williams @ 2014-12-04 13:50 UTC (permalink / raw) To: buildroot Rohit, Under Build Options -> 'strip command for binaries on target', set it to 'none'. Mike On Thu, Dec 4, 2014 at 1:57 AM, Rohit Kumar <rkthebest@gmail.com> wrote: > Hello, > > i am trying to build valgrind into my file system using buildroot. > it compiles without problem. > but when i try to run valgrind it throws me following error: > > ==174== Memcheck, a memory error detector > ==174== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. > ==174== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info > ==174== Command: ./uart /dev/ttyS1 > ==174== > > 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. > > is there any problem in configuration? > configuration file is attached > > kindly help > > With Regards, > > Rohit Kumar > +82 1073149173 > > _______________________________________________ > buildroot mailing list > buildroot at busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] valgrind issues on 2014.11-git buildroot 2014-12-04 13:50 ` Mike Williams @ 2014-12-04 15:26 ` Rohit Kumar 2014-12-04 15:40 ` Mike Williams 0 siblings, 1 reply; 5+ messages in thread From: Rohit Kumar @ 2014-12-04 15:26 UTC (permalink / raw) To: buildroot With Regards, Rohit Kumar +82 1073149173 On Thu, Dec 4, 2014 at 10:50 PM, Mike Williams <mike@mikebwilliams.com> wrote: > Rohit, > > Under Build Options -> 'strip command for binaries on target', set it to > 'none'. > Hello Mike, thank you for the reply. do i need to 'make clean' before 'make' with strip 'none' option? > > Mike > > On Thu, Dec 4, 2014 at 1:57 AM, Rohit Kumar <rkthebest@gmail.com> wrote: > > Hello, > > > > i am trying to build valgrind into my file system using buildroot. > > it compiles without problem. > > but when i try to run valgrind it throws me following error: > > > > ==174== Memcheck, a memory error detector > > ==174== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. > > ==174== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright > info > > ==174== Command: ./uart /dev/ttyS1 > > ==174== > > > > 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. > > > > is there any problem in configuration? > > configuration file is attached > > > > kindly help > > > > With Regards, > > > > Rohit Kumar > > +82 1073149173 > > > > _______________________________________________ > > buildroot mailing list > > buildroot at busybox.net > > http://lists.busybox.net/mailman/listinfo/buildroot > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141205/62ee6b52/attachment.html> ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] valgrind issues on 2014.11-git buildroot 2014-12-04 15:26 ` Rohit Kumar @ 2014-12-04 15:40 ` Mike Williams 2014-12-04 15:56 ` Thomas Petazzoni 0 siblings, 1 reply; 5+ messages in thread From: Mike Williams @ 2014-12-04 15:40 UTC (permalink / raw) To: buildroot I would say yes. I'm not certain of it in this case, but I usually make clean when changing options like this. See: http://buildroot.uclibc.org/downloads/manual/manual.html#full-rebuild Mike On Thu, Dec 4, 2014 at 10:26 AM, Rohit Kumar <rkthebest@gmail.com> wrote: > > With Regards, > > Rohit Kumar > +82 1073149173 > > On Thu, Dec 4, 2014 at 10:50 PM, Mike Williams <mike@mikebwilliams.com> > wrote: >> >> Rohit, >> >> Under Build Options -> 'strip command for binaries on target', set it to >> 'none'. > > Hello Mike, > > thank you for the reply. > do i need to 'make clean' before 'make' with strip 'none' option? >> >> >> Mike >> >> On Thu, Dec 4, 2014 at 1:57 AM, Rohit Kumar <rkthebest@gmail.com> wrote: >> > Hello, >> > >> > i am trying to build valgrind into my file system using buildroot. >> > it compiles without problem. >> > but when i try to run valgrind it throws me following error: >> > >> > ==174== Memcheck, a memory error detector >> > ==174== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. >> > ==174== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright >> > info >> > ==174== Command: ./uart /dev/ttyS1 >> > ==174== >> > >> > 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. >> > >> > is there any problem in configuration? >> > configuration file is attached >> > >> > kindly help >> > >> > With Regards, >> > >> > Rohit Kumar >> > +82 1073149173 >> > >> > _______________________________________________ >> > buildroot mailing list >> > buildroot at busybox.net >> > http://lists.busybox.net/mailman/listinfo/buildroot > > ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] valgrind issues on 2014.11-git buildroot 2014-12-04 15:40 ` Mike Williams @ 2014-12-04 15:56 ` Thomas Petazzoni 0 siblings, 0 replies; 5+ messages in thread From: Thomas Petazzoni @ 2014-12-04 15:56 UTC (permalink / raw) To: buildroot Dear Mike Williams, On Thu, 4 Dec 2014 10:40:45 -0500, Mike Williams wrote: > I would say yes. I'm not certain of it in this case, but I usually > make clean when changing options like this. See: > http://buildroot.uclibc.org/downloads/manual/manual.html#full-rebuild I can confirm you need to do a make clean. Basically, once Buildroot has stripped binaries in output/target, the only sane way to get back to unstripped binaries is to do a full clean build. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-12-04 15:56 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-12-04 6:57 [Buildroot] valgrind issues on 2014.11-git buildroot Rohit Kumar 2014-12-04 13:50 ` Mike Williams 2014-12-04 15:26 ` Rohit Kumar 2014-12-04 15:40 ` Mike Williams 2014-12-04 15:56 ` Thomas Petazzoni
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox