|
From: Naveen K. <g_n...@ya...> - 2009-05-08 18:42:43
|
I dont have the resources to be able to compile it directly on the target right now so I cannot compare the behaviour with this release. Any other suggestions. I ran gdb and this is what I got
-bash-2.05b# gdb /mnt/package/usr/local/valgrind/bin/valgrind
GNU gdb 6.3 (MontaVista 6.3-20.0.79.0601984 2006-11-15)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "powerpc-montavista-linux"...BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 1634559347 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: no group info for section
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 1852112942 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: no group info for section
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 4 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 16 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: no group info for section
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 2 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: no group info for section
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 12 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 12 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 8 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 4 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 262144 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 1634559347 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: no group info for section
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 1852112942 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: no group info for section
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 4 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 16 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: no group info for section
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 2 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: no group info for section
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 12 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 12 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 8 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 4 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 262144 >= 0 for section `'
BFD: /mnt/package/usr/local/valgrind/bin/valgrind: invalid string offset 65536 >= 0 for section `.shstrtab'
(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) r
Starting program: /mnt/package/usr/local/valgrind/bin/valgrind
Program received signal SIGSEGV, Segmentation fault.
0x3000a230 in ?? ()
(gdb) bt
#0 0x3000a230 in ?? ()
#1 0x30028004 in ?? ()
#2 0x30003918 in ?? ()
#3 0x3000faa4 in ?? ()
#4 0x30004a94 in ?? ()
#5 0x30004ed4 in ?? ()
#6 0x30010d8c in ?? ()
warning: Previous frame inner to this frame (corrupt stack?)
(gdb)
----- Original Message ----
From: Bart Van Assche <bar...@gm...>
To: Naveen Kumar <g_n...@ya...>
Cc: val...@li...
Sent: Friday, May 8, 2009 1:46:59 PM
Subject: Re: [Valgrind-developers] cross compiling valgrind
On Fri, May 8, 2009 at 3:14 PM, Naveen Kumar <g_n...@ya...> wrote:
> I am trying to run valgrind on my target platform(PPC/440) after cross compiling it and its gives a seg fault. I ran strace but it doesnt give any meaningful info as it faults after the very first execve call. I am guessing this has something to do with the load address of valgrind. Is there any way I can debug this a bit more ?? My configure options are as follows
>
> ./configure --prefix=/usr/local/valgrind --host=powerpc-montavista-linux --build=i386-redhat-linux AR=/opt/montavista/cge/devkit/ppc/440/bin/ppc_440-ar CC=/opt/montavista/cge/devkit/ppc/440/bin/ppc_440-gcc CXX=/opt/montavista/cge/devkit/ppc/440/bin/ppc_440-g++ LD=/opt/montavista/cge/devkit/ppc/440/bin/ppc_440-ld RANLIB=/opt/montavista/cge/devkit/ppc/440/bin/ppc_440-ranlib LDFLAGS="-L/opt/montavista/cge/devkit/ppc/440/target/usr/lib"
>
> The build itself looks fine and I dont see any build errors or anything amiss. On another note I had long back compiled valgrind directly on target and it had executed fine that time. I am just curious to see why the cross compiling method does not work.
Does Valgrind 3.4.1 work fine when compiled on the target instead of
cross-compiling it ? I'm wondering whether you hit an issue in the
cross-compilation environment.
Bart.
|