|
From: Naveen K. <g_n...@ya...> - 2009-05-08 15:25:02
|
I am using 3.4.1.
----- Original Message ----
From: Bart Van Assche <bar...@gm...>
To: Naveen Kumar <g_n...@ya...>
Cc: val...@li...
Sent: Friday, May 8, 2009 9:28:32 AM
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.
Which Valgrind version are you using ? This issue should have been
fixed in Valgrind 3.4.0.
Bart.
|