|
From: Александар М. <dar...@gm...> - 2011-11-11 15:07:42
|
Hi, first post here. So let's get to the stuff I need help with. I have compiled Valgrind 3.7 using arm-linux-gnueabi compiler with the -static option. When I try to run it, I get this: # . valgrind --leak-check=yes ./system/bin/testapp /system/bin/valgrind: 1: Syntax error: word unexpected (expecting ")") The test app is compiled in the same way, also statically linked. Can anyone please help me with this? I appreciate it. Aleksandar |
|
From: WAROQUIERS P. <phi...@eu...> - 2011-11-11 15:17:02
|
># . valgrind --leak-check=yes ./system/bin/testapp >/system/bin/valgrind: 1: Syntax error: word unexpected (expecting ")") Why do you put a . in front of valgrind ? To my knowledge, this indicates that the shell has to "interpret" this "script". But valgrind is an executable. So, I guess the shell obeys and tries to interpret object code as a script, and reports a syntax error. Does it work to just type: valgrind --leak-check=yes ./system/bin/testapp ? Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |
|
From: Александар М. <dar...@gm...> - 2011-11-11 15:22:09
|
Unfortunately, the . is necessary for some reason. Here's a more complete log. # . /valgrind --leak-check=yes testapp .: Can't open /valgrind # ./valgrind --leak-check=yes testapp ./valgrind: not found # . valgrind --leak-check=yes testapp /system/bin/valgrind: 1: Syntax error: word unexpected (expecting ")") # valgrind --leak-check=yes ./system/bin/testapp valgrind: not found Thanks for your time Phillipe. Aleksandar |
|
From: Alexander P. <gl...@go...> - 2011-11-11 15:34:46
|
Can you try: $ file `which valgrind` and $ head `which valgrind` ? On Fri, Nov 11, 2011 at 7:21 PM, Александар Миленковић <dar...@gm...> wrote: > Unfortunately, the . is necessary for some reason. > > Here's a more complete log. > > # . /valgrind --leak-check=yes testapp > .: Can't open /valgrind > # ./valgrind --leak-check=yes testapp > ./valgrind: not found > # . valgrind --leak-check=yes testapp > /system/bin/valgrind: 1: Syntax error: word unexpected (expecting ")") > # valgrind --leak-check=yes ./system/bin/testapp > valgrind: not found > > Thanks for your time Phillipe. > > Aleksandar > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > -- Alexander Potapenko Software Engineer Google Moscow |
|
From: Александар М. <dar...@gm...> - 2011-11-11 15:30:19
|
<ommited>:/android/external/valgrind-3.7.0/coregrind$ file valgrind
valgrind: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically
linked, for GNU/Linux 2.6.16, not stripped
<ommited>:/android/external/valgrind-3.7.0/coregrind$ head valgrind
ELF ( @�4� 4 ($! p����� � ��ȍȍ� ȍ�
�� -� -� ��� �-� 1 � �����
ȍ ( Q�td GNU �-� ��� �/������� �
��
0��T��#�H��� 0�� �� 0 0��S�
� � �/��
@-�4@�� ���0��S� $0��S�
<0��-�S� �0�� ��@�� �/ᨕ
0��0 ��� �,��0��S�
0��S�
���O-���/� � @��%�`P�&
:����E @@㔟 � �@���� �
��'��pP� �� ��t��`���Pf� �� �� ��Ɏ�0��0�� `�� �� ��
�� � ��� ��
��Y��P�ȅ �@
V��������p@-� �M�M�@�� ��� � @��/ �
@� 0��5� ��/ �����P� ������@�� ��� � @��/ �
@� 0��&� �� �㬖�PP��� ��� � @��/ �
@� 0�� �� �� *�����`������� V���@�� ��� � @��/ � @� 0�� �0��?O� *�
�� 0��#S�2 0��!S�/ V��
Thank you for your response Aleksandr,
Aleksandar
On Fri, Nov 11, 2011 at 4:26 PM, Alexander Potapenko <gl...@go...> wrote:
> Can you try:
>
> $ file `which valgrind`
> and
> $ head `which valgrind`
> ?
>
> On Fri, Nov 11, 2011 at 7:21 PM, Александар Миленковић
> <dar...@gm...> wrote:
>> Unfortunately, the . is necessary for some reason.
>>
>> Here's a more complete log.
>>
>> # . /valgrind --leak-check=yes testapp
>> .: Can't open /valgrind
>> # ./valgrind --leak-check=yes testapp
>> ./valgrind: not found
>> # . valgrind --leak-check=yes testapp
>> /system/bin/valgrind: 1: Syntax error: word unexpected (expecting ")")
>> # valgrind --leak-check=yes ./system/bin/testapp
>> valgrind: not found
>>
>> Thanks for your time Phillipe.
>>
>> Aleksandar
>>
>> ------------------------------------------------------------------------------
>> RSA(R) Conference 2012
>> Save $700 by Nov 18
>> Register now
>> http://p.sf.net/sfu/rsa-sfdev2dev1
>> _______________________________________________
>> Valgrind-users mailing list
>> Val...@li...
>> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>>
>
>
>
> --
> Alexander Potapenko
> Software Engineer
> Google Moscow
>
|
|
From: WAROQUIERS P. <phi...@eu...> - 2011-11-11 15:51:35
|
According to the output below, your valgrind seems to be at least located in /android/external/valgrind-3.7.0/coregrind and so you might try: /android/external/valgrind-3.7.0/coregrind/valgrind But this looks like this Valgrind has not been installed and/or compiled according to the "official way". Cfr my previous mail: I succeeded having a Valgrind running on Android, doing *precisely* what is documented in README.android. It looks like what you did does not match the README.android and this might very well be the source of the problem. Philippe >-----Original Message----- >From: Александар Миленковић [mailto:dar...@gm...] >Sent: Friday 11 November 2011 16:30 >To: Alexander Potapenko >Cc: val...@li... >Subject: Re: [Valgrind-users] Valgrind on Android (Gingerbread) > ><ommited>:/android/external/valgrind-3.7.0/coregrind$ file valgrind >valgrind: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically >linked, for GNU/Linux 2.6.16, not stripped > > ><ommited>:/android/external/valgrind-3.7.0/coregrind$ head valgrind > ELF ( @ 4 4 ($! p ȍȍ ȍ > - - - 1 > ȍ ( Q td GNU - / > > 0 T # H Ć 0 0 0 S > / > @- 4@ 0 S $0 S ><0 - S 0 @ /ᨕ >0 0 , 0 S > 0 S > O- / @ % `P & >: E @@㔟 @ > ' pP t ` Pf Ɏ 0 0 ` > > > Y P ȅ @ >V p@- M M @ @ / >@ 0 5 / P @ @ / >@ 0 & 㬖 PP @ / >@ 0 * ` V @ @ / @ 0 > 0 ?O * > 0 #S 2 0 !S / V > >Thank you for your response Aleksandr, > >Aleksandar > >On Fri, Nov 11, 2011 at 4:26 PM, Alexander Potapenko ><gl...@go...> wrote: >> Can you try: >> >> $ file `which valgrind` >> and >> $ head `which valgrind` >> ? >> >> On Fri, Nov 11, 2011 at 7:21 PM, Александар Миленковић >> <dar...@gm...> wrote: >>> Unfortunately, the . is necessary for some reason. >>> >>> Here's a more complete log. >>> >>> # . /valgrind --leak-check=yes testapp >>> .: Can't open /valgrind >>> # ./valgrind --leak-check=yes testapp >>> ./valgrind: not found >>> # . valgrind --leak-check=yes testapp >>> /system/bin/valgrind: 1: Syntax error: word unexpected >(expecting ")") >>> # valgrind --leak-check=yes ./system/bin/testapp >>> valgrind: not found >>> >>> Thanks for your time Phillipe. >>> >>> Aleksandar >>> >>> >--------------------------------------------------------------- >--------------- >>> RSA(R) Conference 2012 >>> Save $700 by Nov 18 >>> Register now >>> http://p.sf.net/sfu/rsa-sfdev2dev1 >>> _______________________________________________ >>> Valgrind-users mailing list >>> Val...@li... >>> https://lists.sourceforge.net/lists/listinfo/valgrind-users >>> >> >> >> >> -- >> Alexander Potapenko >> Software Engineer >> Google Moscow >> >--------------------------------------------------------------- >--------------- >RSA(R) Conference 2012 >Save $700 by Nov 18 >Register now >http://p.sf.net/sfu/rsa-sfdev2dev1 >_______________________________________________ >Valgrind-users mailing list >Val...@li... >https://lists.sourceforge.net/lists/listinfo/valgrind-users > ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |
|
From: Александар М. <dar...@gm...> - 2011-11-11 16:50:39
|
Thanks for the input, but the thing is - i'm running on a proprietary board (running on ARMv7+VFP); for which android has been specifically ported. I'm avoiding to disclose potentially sensitive (confidential) info, but here's the deal: When I first try to configure with the arm-eabi compiler I got with this SDK, valgrind doesn't recognize the OS and returns... then i configure it with arm-linux-gnueabi, i've added support for all ARM processors (config.sh, line 5288 or so, changed armv7* to arm*) and that goes well. After I get the compiled binary, I put it in the rootfs folder used for booting up the board, like any other file. That's why I know it's not a PATH issue, because it's the exact same procedure i do for every other app and they *always* get found without absolute pathing. >From what I understood, the "official" way states that it only works on Nexus S, but I know for sure it can run on our board as well - some collegues (which i can't get hold of currently) have used it without too much hassle. But here's what it is: android sdk is on my VM. the rootfs is on the board. there is no /external/valgrind/coregrind/valgrind on the board, it's just /system/bin/valgrind. Every other app I put there becomes "visible" instantly as i work with a live NFS. I really don't know why valgrind is acting up and pretending not to be there when it clearly IS there. I can't even get it to scan through LS, so a hello_world.c won't do me much good either I suppose... but I can try. So, how do I help you help me without breaching any NDAs? :) P.S. I have to compile Valgrind with -static (err... link it statically) for it to run on the board when using the said arm-linux-gnueabi compiler. |
|
From: WAROQUIERS P. <phi...@eu...> - 2011-11-11 16:58:09
|
> >But here's what it is: >android sdk is on my VM. the rootfs is on the board. there is no >/external/valgrind/coregrind/valgrind on the board, it's just >/system/bin/valgrind. Every other app I put there becomes "visible" >instantly as i work with a live NFS. I really don't know why valgrind >is acting up and pretending not to be there when it clearly IS there. valgrind is not a typical application, and just copy "valgrind" is to my knowledge not going to work. Which "configure" command did you use ? Which "make" and "make install" command did you use ? Did you (and how?) "push" your valgrind onto the Android ? Or do you assume that the compiled and installed valgrind on the sdk visible through NFS is automatically working ? (in other words, you might indicate the differences between what you are doing and what is indicated in the README.android). Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |
|
From: Александар М. <dar...@gm...> - 2011-11-11 17:14:00
|
Sure,
once I extracted the valgrind-3.7 tarball into android/external, i
just went into the folder and used this
$ ./configure --build i686-pc-linux-gnu --host arm-marvell-linux-gnueabi
Then configuration proceeded fine... once everything was setup, it was easy
$make clean; make
Both passing good and with no errors.
Then I go into /valgrind-3.7/coregrind and pick up the file from
there, and put it in a folder which is used as the root file system of
the board. A faster alternative to adb pushing really.
So whichever kind of app Valgrind is, I was guessing that I'll
probably be missing some binaries which is why i compiled it
statically.
I even went as far as to put it in /tmp/ folder, enter the folder and
try to call it. So... here's what I did to get up to here.
$ ./configure --build i686-pc-linux-gnu --host arm-marvell-eabi
checking host system type... arm-marvell-eabi
checking for a supported CPU... no (arm)
configure: error: Unsupported host architecture. Sorry
** I go into the configure script and fix that. ***
$ ./configure --build i686-pc-linux-gnu --host arm-marvell-eabi
checking for a supported CPU... ok (arm)
checking for a 64-bit only build... no
checking for a 32-bit only build... no
checking for a supported OS... no (eabi)
this one I wasn't going to fix so instead I just did
$ ./configure --build i686-pc-linux-gnu --host arm-marvell-linux-gnueabi
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-marvell-linux-gnueabi-strip... arm-marvell-linux-gnueabi-strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for arm-marvell-linux-gnueabi-gcc...
/scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
. . . . . . .
Maximum build arch: arm
Primary build arch: arm
Secondary build arch:
Build OS: linux
Primary build target: ARM_LINUX
Secondary build target:
Platform variant: vanilla
Primary -DVGPV string: -DVGPV_arm_linux_vanilla=1
Default supp files: exp-sgcheck.supp xfree-3.supp
xfree-4.supp glibc-2.X-drd.supp glibc-2.34567-NPTL-helgrind.supp
glibc-2.X.supp
Now, the only difference between the readme.android and this I see is
that in the readme, they say i should see this:
# Platform variant: android
# Primary -DVGPV string: -DVGPV_arm_linux_android=1
... so, how do I hack this platform variant to return a proper result? :)
|
|
From: WAROQUIERS P. <phi...@eu...> - 2011-11-12 10:47:29
|
>once I extracted the valgrind-3.7 tarball into android/external, i >just went into the folder and used this >$ ./configure --build i686-pc-linux-gnu --host >arm-marvell-linux-gnueabi > >Then configuration proceeded fine... once everything was >setup, it was easy >$make clean; make >Both passing good and with no errors. > >Then I go into /valgrind-3.7/coregrind and pick up the file from >there, and put it in a folder which is used as the root file system of >the board. A faster alternative to adb pushing really. > >So whichever kind of app Valgrind is, I was guessing that I'll >probably be missing some binaries which is why i compiled it >statically. Effectively, I believe you are guessing properly one source of a problem, but for sure, the way you expect to solve this will *not* solve it. Valgrind is not a single executable, it is made of several executables, and scripts, and files and dynamic libraries. So, on this side, you should really follow README.android and use adb push etc. You might lose 2 minutes due to the adb push, but this will very probably spare hours of mysteries investigations. It looks like what you are trying to do is quite different of what has been tested and documented in README.android. A.o. if you try to just copy the valgrind, this will *not* work. Valgrind cannot be build statically as one single executable. You much better do make install etc. Probably the best is to start by having the minimal differences between the README.android and your actions. And when something does not work as documented, solve it so that you can continue the rest of the actions similarly. So, define the env variables as explained (pointing to your SDK), etc etc. >... so, how do I hack this platform variant to return a proper >result? :) You will probably need some changes in configure.in and similar and then re-run ./autogen.sh before the configure. But I have a close to zero knowledge of automake/autoconf and related, and so can't help you in this area (even if I would have access to a platform similar to yours). Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |
|
From: Julian S. <js...@ac...> - 2011-11-12 16:16:11
|
> Now, the only difference between the readme.android and this I see is > that in the readme, they say i should see this: > # Platform variant: android > # Primary -DVGPV string: -DVGPV_arm_linux_android=1 > > ... so, how do I hack this platform variant to return a proper result? :) It would be much better if you actually followed the instructions in README.android exactly, and report on what results you got. J |
|
From: Александар М. <dar...@gm...> - 2011-11-15 10:03:51
|
Thanks for the replies so far! But I don't see a autogen.sh script in Valgrind root. The ones i do have are as follows compile, config.guess, config.status, configure, depcomp, install-sh, missing and vg-in-place So thats why i deviated from the readme in the first place. Where do I find the referenced autogen.sh ? Thanks, Aleksandar |
|
From: Julian S. <js...@ac...> - 2011-11-15 10:32:39
|
On Tuesday, November 15, 2011, Александар Миленковић wrote: > Thanks for the replies so far! > > But I don't see a autogen.sh script in Valgrind root. The ones i do > have are as follows > compile, config.guess, config.status, configure, depcomp, install-sh, > missing and vg-in-place > > So thats why i deviated from the readme in the first place. Where do I > find the referenced autogen.sh ? Hmm, this is a documentation bug. For builds from a tarball, you can skip the ./autogen.sh step, and continue directly with the ./configure step. J |
|
From: Александар М. <dar...@gm...> - 2011-11-15 11:01:29
|
Also, this part is confusing me a little bit CPPFLAGS="--sysroot=$NDKROOT/platforms/android-3/arch-arm -DANDROID_HARDWARE_$HWKIND" \ CFLAGS="--sysroot=$NDKROOT/platforms/android-3/arch-arm" \ ./configure --prefix=/data/local/Inst \ --host=armv7-unknown-linux --target=armv7-unknown-linux \ --with-tmpdir=/tmp/valgrind Should I edit it into config.sh or just define it as a environment variable? On Tue, Nov 15, 2011 at 11:26 AM, Julian Seward <js...@ac...> wrote: > On Tuesday, November 15, 2011, Александар Миленковић wrote: >> Thanks for the replies so far! >> >> But I don't see a autogen.sh script in Valgrind root. The ones i do >> have are as follows >> compile, config.guess, config.status, configure, depcomp, install-sh, >> missing and vg-in-place >> >> So thats why i deviated from the readme in the first place. Where do I >> find the referenced autogen.sh ? > > Hmm, this is a documentation bug. For builds from a tarball, you can skip > the ./autogen.sh step, and continue directly with the ./configure step. > > J > |
|
From: Александар М. <dar...@gm...> - 2011-11-15 11:44:23
|
So here's what I've got so far...
$export HWKIND=nexus_s //it's neither nexus nor pandaboard so i'll
try to fake it.
$export NDKROOT=/scratch/workareas/android/prebuilt/ndk
$cd /scratch/workareas/android/external/Valgrind
$export AR=/scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-ar
$export LD=/scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-ld
$export CC=/scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-gcc
//yes, i'm not using the default NDK compiler because that one doesn't
get recognized and ./configure fails
$ ./configure --build i686-pc-linux-gnu --host arm-marvell-linux-gnueabi
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-marvell-linux-gnueabi-strip... arm-marvell-linux-gnueabi-strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for arm-marvell-linux-gnueabi-gcc...
/scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether
/scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-gcc
accepts -g... yes
checking for /scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-gcc
option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of
/scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-gcc...
gcc3
checking whether
/scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-gcc
and cc understand -c and -o together... yes
checking how to run the C preprocessor...
/scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-gcc
-E
checking for arm-marvell-linux-gnueabi-g++... arm-marvell-linux-gnueabi-g++
checking whether we are using the GNU C++ compiler... yes
checking whether arm-marvell-linux-gnueabi-g++ accepts -g... yes
checking dependency style of arm-marvell-linux-gnueabi-g++... gcc3
checking for arm-marvell-linux-gnueabi-ranlib...
arm-marvell-linux-gnueabi-ranlib
checking for a sed that does not truncate output... /bin/sed
checking for perl... /usr/bin/perl
checking for gdb... /usr/bin/gdb
checking dependency style of
/scratch/workareas/MV88DE3100_SDK/SDK_Tools/cross_toolchain/tarballs/4.4.5/arm-marvell-linux-gnueabi-4.4.5/bin/arm-marvell-linux-gnueabi-gcc...
gcc3
checking for diff -u... yes
checking for a supported version of gcc... ok (4.4.5.)
checking build system type... i686-pc-linux-gnu
checking host system type... arm-marvell-linux-gnueabi
checking for a supported CPU... ok (arm)
checking for a 64-bit only build... no
checking for a 32-bit only build... no
checking for a supported OS... ok (linux-gnueabi)
checking for the kernel version... 2.6.x/3.x family (2.6.35-22-generic)
checking for a supported CPU/OS combination... ok (arm-linux-gnueabi)
checking for use as an inner Valgrind... no
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking features.h usability... yes
checking features.h presence... yes
checking for features.h... yes
checking the GLIBC_VERSION version... 2.11 family
checking for CLOCK_MONOTONIC... yes
checking for pthread_rwlock_t... yes
checking for PTHREAD_MUTEX_ADAPTIVE_NP... yes
checking for PTHREAD_MUTEX_ERRORCHECK_NP... yes
checking for PTHREAD_MUTEX_RECURSIVE_NP... yes
checking for PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP... yes
checking for pthread_mutex_t.__m_kind... no
checking for pthread_mutex_t.__data.__kind... yes
checking for Altivec... no
checking for VSX... no
checking for pthread_create@GLIBC2.0()... no
checking for eventfd()... yes
checking if gcc accepts -m32... no
checking if gcc accepts -m64... no
checking if gcc accepts -mmmx... no
checking if gcc accepts -msse... no
checking if gcc accepts -mpreferred-stack-boundary... no
checking if gcc accepts -Wno-pointer-sign... yes
checking if gcc accepts -Wno-empty-body... yes
checking if gcc accepts -Wno-format-zero-length... yes
checking if gcc accepts -Wno-nonnull... yes
checking if gcc accepts -Wno-overflow... yes
checking if gcc accepts -Wno-uninitialized... yes
checking if gcc accepts -Wextra or -W... -Wextra
checking if gcc accepts -fno-stack-protector... yes
checking if gcc accepts --param inline-unit-growth... yes
checking if the linker accepts -Wl,--build-id=none... yes
checking if ppc32/64 as supports mtocrf/mfocrf... no
checking if x86/amd64 assembler speaks SSE3... no
checking if x86/amd64 assembler speaks SSSE3... no
checking if x86/amd64 assembler supports 'pclmulqdq'... no
checking if x86/amd64 assembler supports 'lzcnt'... no
checking if x86/amd64 assembler speaks SSE4.2... no
checking for TLS support... yes
checking for ANSI C header files... (cached) yes
checking asm/unistd.h usability... yes
checking asm/unistd.h presence... yes
checking for asm/unistd.h... yes
checking endian.h usability... yes
checking endian.h presence... yes
checking for endian.h... yes
checking mqueue.h usability... yes
checking mqueue.h presence... yes
checking for mqueue.h... yes
checking sys/endian.h usability... no
checking sys/endian.h presence... no
checking for sys/endian.h... no
checking sys/epoll.h usability... yes
checking sys/epoll.h presence... yes
checking for sys/epoll.h... yes
checking sys/eventfd.h usability... yes
checking sys/eventfd.h presence... yes
checking for sys/eventfd.h... yes
checking sys/klog.h usability... yes
checking sys/klog.h presence... yes
checking for sys/klog.h... yes
checking sys/poll.h usability... yes
checking sys/poll.h presence... yes
checking for sys/poll.h... yes
checking sys/signal.h usability... yes
checking sys/signal.h presence... yes
checking for sys/signal.h... yes
checking sys/signalfd.h usability... yes
checking sys/signalfd.h presence... yes
checking for sys/signalfd.h... yes
checking sys/syscall.h usability... yes
checking sys/syscall.h presence... yes
checking for sys/syscall.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for sys/types.h... (cached) yes
checking if <linux/futex.h> is usable... yes
checking for uid_t in sys/types.h... yes
checking for off_t... yes
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking for working memcmp... no
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for sys/param.h... yes
checking for getpagesize... yes
checking for working mmap... no
checking for pthread_create in -lpthread... yes
checking for clock_gettime in -lrt... yes
checking for clock_gettime... yes
checking for epoll_create... yes
checking for epoll_pwait... yes
checking for klogctl... yes
checking for mallinfo... yes
checking for memchr... yes
checking for memset... yes
checking for mkdir... yes
checking for mremap... yes
checking for ppoll... yes
checking for pthread_barrier_init... yes
checking for pthread_condattr_setclock... yes
checking for pthread_mutex_timedlock... yes
checking for pthread_rwlock_timedrdlock... yes
checking for pthread_rwlock_timedwrlock... yes
checking for pthread_spin_lock... yes
checking for pthread_yield... yes
checking for readlinkat... yes
checking for semtimedop... yes
checking for signalfd... yes
checking for sigwaitinfo... yes
checking for strchr... yes
checking for strdup... yes
checking for strpbrk... yes
checking for strrchr... yes
checking for strstr... yes
checking for syscall... yes
checking for utimensat... yes
checking primary target for usable MPI2-compliant C compiler and mpi.h... no
checking secondary target for usable MPI2-compliant C compiler and mpi.h... no
checking for boost... no
checking for OpenMP... yes
checking if gcc supports __sync_bool_compare_and_swap... yes
checking if g++ supports __sync_bool_compare_and_swap... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating VEX/Makefile
config.status: creating valgrind.spec
config.status: creating valgrind.pc
config.status: creating glibc-2.X.supp
config.status: creating docs/Makefile
config.status: creating tests/Makefile
config.status: creating tests/vg_regtest
config.status: creating perf/Makefile
config.status: creating perf/vg_perf
config.status: creating gdbserver_tests/Makefile
config.status: creating include/Makefile
config.status: creating auxprogs/Makefile
config.status: creating mpi/Makefile
config.status: creating coregrind/Makefile
config.status: creating memcheck/Makefile
config.status: creating memcheck/tests/Makefile
config.status: creating memcheck/tests/amd64/Makefile
config.status: creating memcheck/tests/x86/Makefile
config.status: creating memcheck/tests/linux/Makefile
config.status: creating memcheck/tests/darwin/Makefile
config.status: creating memcheck/tests/amd64-linux/Makefile
config.status: creating memcheck/tests/x86-linux/Makefile
config.status: creating memcheck/tests/ppc32/Makefile
config.status: creating memcheck/tests/ppc64/Makefile
config.status: creating memcheck/perf/Makefile
config.status: creating cachegrind/Makefile
config.status: creating cachegrind/tests/Makefile
config.status: creating cachegrind/tests/x86/Makefile
config.status: creating cachegrind/cg_annotate
config.status: creating cachegrind/cg_diff
config.status: creating callgrind/Makefile
config.status: creating callgrind/callgrind_annotate
config.status: creating callgrind/callgrind_control
config.status: creating callgrind/tests/Makefile
config.status: creating helgrind/Makefile
config.status: creating helgrind/tests/Makefile
config.status: creating massif/Makefile
config.status: creating massif/tests/Makefile
config.status: creating massif/perf/Makefile
config.status: creating massif/ms_print
config.status: creating lackey/Makefile
config.status: creating lackey/tests/Makefile
config.status: creating none/Makefile
config.status: creating none/tests/Makefile
config.status: creating none/tests/amd64/Makefile
config.status: creating none/tests/ppc32/Makefile
config.status: creating none/tests/ppc64/Makefile
config.status: creating none/tests/x86/Makefile
config.status: creating none/tests/arm/Makefile
config.status: creating none/tests/s390x/Makefile
config.status: creating none/tests/linux/Makefile
config.status: creating none/tests/darwin/Makefile
config.status: creating none/tests/x86-linux/Makefile
config.status: creating exp-sgcheck/Makefile
config.status: creating exp-sgcheck/tests/Makefile
config.status: creating drd/Makefile
config.status: creating drd/scripts/download-and-build-splash2
config.status: creating drd/tests/Makefile
config.status: creating exp-bbv/Makefile
config.status: creating exp-bbv/tests/Makefile
config.status: creating exp-bbv/tests/x86/Makefile
config.status: creating exp-bbv/tests/x86-linux/Makefile
config.status: creating exp-bbv/tests/amd64-linux/Makefile
config.status: creating exp-bbv/tests/ppc32-linux/Makefile
config.status: creating exp-bbv/tests/arm-linux/Makefile
config.status: creating exp-dhat/Makefile
config.status: creating exp-dhat/tests/Makefile
config.status: creating coregrind/link_tool_exe_linux
config.status: creating coregrind/link_tool_exe_darwin
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
Maximum build arch: arm
Primary build arch: arm
Secondary build arch:
Build OS: linux
Primary build target: ARM_LINUX
Secondary build target:
Platform variant: vanilla
Primary -DVGPV string: -DVGPV_arm_linux_vanilla=1
Default supp files: exp-sgcheck.supp xfree-3.supp
xfree-4.supp glibc-2.X-drd.supp glibc-2.34567-NPTL-helgrind.supp
glibc-2.X.supp
//still in Valgrind
$ cd ../../out/target/product/berlin_bg2/system/bin/
$ file valgrind
valgrind: ELF 32-bit LSB executable, ARM, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.16, not
stripped
---------------
So, if this could be considered "working" I'll try alternatives of adb
pushing / copying stuff to proper places.
Thanks for helping so far,
Aleksandar
|
|
From: David C. <dcc...@ac...> - 2011-11-11 15:40:53
|
On 11/11/2011 7:21 AM, Александар Миленковић wrote:
> Unfortunately, the . is necessary for some reason.
>
> Here's a more complete log.
>
> # . /valgrind --leak-check=yes testapp
> .: Can't open /valgrind
> # ./valgrind --leak-check=yes testapp
> ./valgrind: not found
> # . valgrind --leak-check=yes testapp
> /system/bin/valgrind: 1: Syntax error: word unexpected (expecting ")")
> # valgrind --leak-check=yes ./system/bin/testapp
> valgrind: not found
>
>
What happens if you run "/system/bin/valgrind --leak-check=yes
testapp"? It seems that valgrind is installed in /system/bin.
What is the search path in the shell? If the search path does not
include the directory in which valgrind is located, the shell will have
trouble finding it.
--
David Chapman dcc...@ac...
Chapman Consulting -- San Jose, CA
|
|
From: WAROQUIERS P. <phi...@eu...> - 2011-11-11 15:37:28
|
># . /valgrind --leak-check=yes testapp >.: Can't open /valgrind ># ./valgrind --leak-check=yes testapp >./valgrind: not found ># . valgrind --leak-check=yes testapp >/system/bin/valgrind: 1: Syntax error: word unexpected (expecting ")") ># valgrind --leak-check=yes ./system/bin/testapp >valgrind: not found I suggest you try with absolute paths both for valgrind and the testapp. E.g. assuming valgrind is in the directory /somewhere/where/you/find/valgrind and your testapp is in the directory /theplace/where/you/find/testapp type: /somewhere/where/you/find/valgrind --leak-check=yes /theplace/where/you/find/testapp This should avoid PATH problems. Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |
|
From: Александар М. <dar...@gm...> - 2011-11-11 15:41:19
|
Thanks for the suggestion Philippe but I already did. # . /system/bin/valgrind ls /system/bin/valgrind: 1: Syntax error: word unexpected (expecting ")") # /system/bin/valgrind ls /system/bin/valgrind: not found The way I see it, it doesn't matter if it's a PATH thing or not... I can't even get the basic 'demo run' of ls or any other app. I'm getting slightly frustrated being stuck on this stupid step #1. Thanks for helping, Aleksandar |
|
From: Dan K. <da...@ke...> - 2011-11-11 15:48:29
|
Try compiling a "hello, world" c program with the same compiler and compiler flags you used for valgrind. Maybe it's generating an executable type your system doesn't recognize. |
|
From: Baurzhan I. <ib...@ra...> - 2011-11-11 15:47:47
|
On Fri, Nov 11, 2011 at 04:07:13PM +0100, Александар Миленковић wrote: > # . valgrind --leak-check=yes ./system/bin/testapp > /system/bin/valgrind: 1: Syntax error: word unexpected (expecting ")") Have you intended to start ./valgrind? With kind regards, Baurzhan. |