|
From: Gopal R. p. <gop...@gm...> - 2016-02-07 14:03:53
|
Dear All, I am facing issue in porting valgrind on arm-linux, can anyone help me in this respect. Regards, Gopal |
|
From: Rhys K. <rhy...@gm...> - 2016-02-07 16:17:12
|
Gopal, You'll need to be more specific outlining the issues you are seeing with Valgrind on ARM/Linux. That said, the current version should support many of the variants on that platform, as per the documentation: It runs on the following platforms: X86/Linux, AMD64/Linux, ARM/Linux, ARM64/Linux, ... ARM/Android (2.3.x and later), ARM64/Android, ... and AMD64/Darwin (Mac OS X 10.10, with initial support for 10.11). Regards, Rhys On 7 February 2016 at 09:03, Gopal Reddy pandiri <gop...@gm...> wrote: > Dear All, > I am facing issue in porting valgrind on arm-linux, can anyone help me in > this respect. > > Regards, > Gopal > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > > |
|
From: Gopal R. p. <gop...@gm...> - 2016-02-08 08:30:13
|
Thanks Rhys, I was able to successfully compile on arm-Linux while trying to run on the device(with arm-linux), Valgrind at the startup throws the following errors. *root@iCAM7000S:bin# ./valgrind --leak-check=yes /usr/local/bin/icammgr/iCamManager7000S -qws* *==1106== Memcheck, a memory error detector* *==1106== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.* *==1106== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info* *==1106== Command: /usr/local/bin/icammgr/iCamManager7000S -qws* *==1106== * *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.* Let me know if any further information required. Regards, Gopal Reddy P. On Sun, Feb 7, 2016 at 9:47 PM, Rhys Kidd <rhy...@gm...> wrote: > Gopal, > > You'll need to be more specific outlining the issues you are seeing with > Valgrind on ARM/Linux. That said, the current version should support many > of the variants on that platform, as per the documentation: > > It runs on the following platforms: X86/Linux, AMD64/Linux, ARM/Linux, > ARM64/Linux, ... ARM/Android (2.3.x and later), ARM64/Android, ... and > AMD64/Darwin (Mac OS X 10.10, with initial support for 10.11). > > Regards, > Rhys > > On 7 February 2016 at 09:03, Gopal Reddy pandiri <gop...@gm...> > wrote: > >> Dear All, >> I am facing issue in porting valgrind on arm-linux, can anyone help me in >> this respect. >> >> Regards, >> Gopal >> >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >> _______________________________________________ >> Valgrind-developers mailing list >> Val...@li... >> https://lists.sourceforge.net/lists/listinfo/valgrind-developers >> >> > |
|
From: John R. <jr...@bi...> - 2016-02-08 13:47:49
|
> *==1106== Memcheck, a memory error detector* > *==1106== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.* > *==1106== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info* > *==1106== Command: /usr/local/bin/icammgr/iCamManager7000S -qws* > *==1106== * > * > * > *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.* > > > Let me know if any further information required. There is no more information that is required. All the needed information is contained in that message from valgrind. *You*, *yourself*, must do what it says under "Possible fixes". |