|
From: tic t. <hot...@ho...> - 2008-12-02 17:16:25
|
Hello,
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.
Thanks,
Sebastien.
==2092== Conditional jump or move depends on uninitialised value(s)
==2092== at 0xFDF78A8: unixOpen (os_unix.c:2419)
==2092== by 0xFDF6200: sqlite3OsOpen (os.c:134)
==2092== by 0xFDFB344: pager_open_journal (pager.c:3835)
==2092== by 0xFDDD604: sqlite3BtreeBeginTrans (btree.c:1862)
==2092== by 0xFE10408: sqlite3VdbeExec (vdbe.c:2534)
==2092== by 0xFE1638C: sqlite3_step (vdbeapi.c:330)
==2092== by 0x10053580: CppSQLite3DB::execQuery(char const*) (CppSQLite3.cpp:1270)
==2092== by 0x1001BA04: PortalDBIntf::checkWidgetStatus(std::list<std::string, std::allocator<std::string> >&) (ppsDBIntf.cpp:1156)
==2092== by 0x1000FEA8: PersonalPortal::start() (personalPortal.cpp:244)
==2092== by 0x1002EC14: Interface::StartInterface(void*) (Interface.cpp:48)
==2092== by 0x10014158: main (ppService.cpp:122)
unrecognized PowerPC instruction: 7D20009D
at 0xFDF6E20: openDirectory (os_unix.c:2304)
==2092==
==2092== Process terminating with default action of signal 4 (SIGILL): dumping core
==2092== Illegal opcode at address 0x70090DB8
==2092== at 0xFDF6E20: openDirectory (os_unix.c:2304)
==2092== by 0xFDF78B4: unixOpen (os_unix.c:2420)
==2092== by 0xFDF6200: sqlite3OsOpen (os.c:134)
==2092== by 0xFDFB344: pager_open_journal (pager.c:3835)
==2092== by 0xFDDD604: sqlite3BtreeBeginTrans (btree.c:1862)
==2092== by 0xFE10408: sqlite3VdbeExec (vdbe.c:2534)
==2092== by 0xFE1638C: sqlite3_step (vdbeapi.c:330)
==2092== by 0x10053580: CppSQLite3DB::execQuery(char const*) (CppSQLite3.cpp:1270)
==2092== by 0x1001BA04: PortalDBIntf::checkWidgetStatus(std::list<std::string, std::allocator<std::string> >&) (ppsDBIntf.cpp:1156)
==2092== by 0x1000FEA8: PersonalPortal::start() (personalPortal.cpp:244)
==2092== by 0x1002EC14: Interface::StartInterface(void*) (Interface.cpp:48)
==2092== by 0x10014158: main (ppService.cpp:122)
|
|
From: Bart V. A. <bar...@gm...> - 2008-12-02 17:37:41
|
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. |
|
From: tic t. <hot...@ho...> - 2008-12-02 18:03:39
|
Hi Bart, Thanks a lot for the patch URL, I actually had to mess with the genoffests compilation for latest 3.x versions, so this may be the source of the problems I had at runtime with that version ...; let me try and see how it goes, I'm actually using PPC440EPX but that should be close enough. thanks! Oh, no hiding, name is Sebastien, alias is 'tic tac' :) > 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. |
|
From: tic t. <hot...@ho...> - 2008-12-02 18:29:03
|
Hi Bart, Thanks a lot for the patch URL, I actually had to mess with the genoffests compilation for latest 3.x versions, so this may be the source of the problems I had at runtime with that version ...; let me try and see how it goes, I'm actually using PPC440EPX but that should be close enough. thanks! Oh, no hiding, name is Sebastien, alias is 'tic tac' :) > 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. |
|
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. |
|
From: tic t. <hot...@ho...> - 2008-12-02 22:38:35
|
I am also getting the same floating point exception with 3.3.1 and a similar stacktrace (but for linenums): (gdb) bt #0 0x380206d0 in vgPlain_machine_get_hwcaps () at m_machine.c:404 #1 0x38021b5c in valgrind_main (argc=2, argv=0x7fda8c94, envp=0x7fda8ca0) at m_main.c:1312 #2 0x38024874 in _start_in_C_linux (pArgc=0x7fda8c90) at m_main.c:2327 #3 0x38020de0 in _start () Should I submit a ticket or is there something obvious I should first try? From: hot...@ho... To: bar...@gm... Date: Tue, 2 Dec 2008 14:15:01 -0600 CC: val...@li... Subject: Re: [Valgrind-users] valgrind and powerpc 440 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. |
|
From: Bart V. A. <bar...@gm...> - 2008-12-04 08:39:14
|
On Tue, Dec 2, 2008 at 11:38 PM, tic tac <hot...@ho...> wrote:
> I am also getting the same floating point exception with 3.3.1 and a similar
> stacktrace (but for linenums):
>
> (gdb) bt
> #0 0x380206d0 in vgPlain_machine_get_hwcaps () at m_machine.c:404
> #1 0x38021b5c in valgrind_main (argc=2, argv=0x7fda8c94, envp=0x7fda8ca0)
> at m_main.c:1312
> #2 0x38024874 in _start_in_C_linux (pArgc=0x7fda8c90) at m_main.c:2327
> #3 0x38020de0 in _start ()
>
> Should I submit a ticket or is there something obvious I should first try?
A source code comment in m_machine.c says the following:
/* ppc32 doesn't seem to have a sane way to find out what insn
sets the CPU supports. So we have to arse around with
SIGILLs. Yuck. */
Unless someone on this list has another suggestion, I propose you
submit a bug report. More information about the CPU and the
instruction set supported by the CPU (e.g. an URL to the manual) will
probably help.
Bart.
|
|
From: tic t. <hot...@ho...> - 2008-12-04 21:19:27
|
Thanks, I will submit a ticket mentioning http://tree.celinuxforum.org/CelfPubWiki/BookEandPpc440 > Date: Thu, 4 Dec 2008 09:39:09 +0100 > From: bar...@gm... > To: hot...@ho... > Subject: Re: [Valgrind-users] valgrind and powerpc 440 > CC: val...@li... > > On Tue, Dec 2, 2008 at 11:38 PM, tic tac <hot...@ho...> wrote: > > I am also getting the same floating point exception with 3.3.1 and a similar > > stacktrace (but for linenums): > > > > (gdb) bt > > #0 0x380206d0 in vgPlain_machine_get_hwcaps () at m_machine.c:404 > > #1 0x38021b5c in valgrind_main (argc=2, argv=0x7fda8c94, envp=0x7fda8ca0) > > at m_main.c:1312 > > #2 0x38024874 in _start_in_C_linux (pArgc=0x7fda8c90) at m_main.c:2327 > > #3 0x38020de0 in _start () > > > > Should I submit a ticket or is there something obvious I should first try? > > A source code comment in m_machine.c says the following: > > /* ppc32 doesn't seem to have a sane way to find out what insn > sets the CPU supports. So we have to arse around with > SIGILLs. Yuck. */ > > Unless someone on this list has another suggestion, I propose you > submit a bug report. More information about the CPU and the > instruction set supported by the CPU (e.g. an URL to the manual) will > probably help. > > Bart. |