|
From: tic t. <hot...@ho...> - 2008-12-02 20:15:06
|
Hi, FYI I am getting a floating point exception with memcheck core dumped at startup with trunk (and no other trace), I think I had the same problem with trunk before. Here follows what I did, let me know if you need me to send the core file. I am going to try with 3.3.1 instead in a bit. uname -mr 2.6.18_pro500-440epx_eval ppc svn co svn://svn.valgrind.org/valgrind/trunk valgrind svn cat svn://svn.valgrind.org/valgrind/branches/CROSS_COMPILATION/vex-cross-compilation.patch | patch -p0 svn status X VEX Performing status on external item at 'VEX' ? VEX/auxprogs/genoffsets.s M VEX/auxprogs/genoffsets.c M VEX/Makefile ./configure --build=i686-linux --host=powerpc-montavista-linux-gnu --target=powerpc-montavista-linux-gnu CC=ppc_440ep-gcc CXX=ppc_440ep-g++ LD=ppc_440ep-ld LDD=ppc_440ep-ldd AR=ppc_440ep-ar AS=ppc_440ep-as NM=ppc_440ep-nm STRIP=ppc_440ep-strip RANLIB=ppc_440ep-ranlib OBJDUMP=ppc_440ep-objdump CPPFLAGS=-I/opt/montavista/pro/devkit/ppc/440ep/target/usr/include/ LDFLAGS=-L/opt/montavista/pro/devkit/ppc/440ep/target/usr/lib/ --prefix=/root/valgrind make ; make install /root/valgrind/bin/valgrind $MYBIN Floating point exception (core dumped) (gdb) info threads * 1 process 8932 0x3802e1e0 in vgPlain_machine_get_hwcaps () at m_machine.c:454 (gdb) bt #0 0x3802e1e0 in vgPlain_machine_get_hwcaps () at m_machine.c:454 #1 0x3802f974 in valgrind_main (argc=2, argv=0x7f930c94, envp=0x7f930ca0) at m_main.c:1390 #2 0x38032a28 in _start_in_C_linux (pArgc=0x7f930c90) at m_main.c:2492 #3 0x3802ea50 in _start () > Date: Tue, 2 Dec 2008 18:37:37 +0100 > From: bar...@gm... > To: hot...@ho... > Subject: Re: [Valgrind-users] valgrind and powerpc 440 > CC: val...@li... > > On Tue, Dec 2, 2008 at 6:16 PM, tic tac <hot...@ho...> wrote: > > I did try to cross compile valgrind-2.4.1-ppc for ppc440 and I am getting > > the following "unrecognized PowerPC instruction: 7D20009D" problem with > > sqlite 3.5.4 at runtime. I was wondering if anybody ever tried to > > crosscompile valgrind for ppc440 and/or would have any suggestion on how to > > get by this problem. I am having other unrelated problems with latest > > valgrind versions cross compilation, which is why I rolled back to 2.4.1. > > Valgrind 2.4.1 is really old. Can you please test whether the issue is > still present in the trunk version of Valgrind ? You need to apply the > patch attached to https://bugs.kde.org/show_bug.cgi?id=162295 in order > to make cross-compilation possible. > > I have been using different Valgrind 3.x versions on the PowerPC 440GX > myself extensively. > > BTW: you are the first one who posts a message on this list without > revealing his or her own name. > > Bart. |