I've had the same problem, but saw a colleague using "DESTDIR" when
building some other project (See the make install command). This also
works with valgrind. I build valgrind with this script:
**
export location=$(pwd)
#Path to compiler:
export
TARGET_TOOL_BASE=/opt
Hi,
I don't know if this helps you, but what is the output from configure?
configure checks for altivec support, and it seems to me like this isn't
supported by your compiler.
I run valgrind on a ppc. The (cross)compiler (4.1.2) supports altivec, but
the CPU doesn't. And valgrind builds and ru
Hi,
I have seen the first one (the valgrind error) on my PPC embedded target.
The solution in my case was to build the OS with debug info. (In fact
replacing ld.so without debug info with an ld.so with debug info solved
the problem).
/Mogens
naeem memon
07-05-2010 07:54
To
valgrind-user
program runs fine on
my CPU. I will investigate this is pure luck, or dcbzl really is
supported.
I will also take a deeper look into how FFmpeg is handling/using this
instruction.
Thanks very much for your help so far!
-Mogens
Dave Goodell
14-04-2010 19:35
To
Mogens Lindholdt Lauridsen
it.
So I have changed your test program so the BLOCK_SIZE is 32. And now the
program can run on my target. However valgrind crashed because of the
"vassert(lineszB == 128);" in you patch.
I have also changed this, and now it works!
-Mogens
Dave Goodell
14-04-2010 00:01
To
Mogens Lin
Rerun with --leak-check=full to see details of leaked memory
==823==
==823== For counts of detected and suppressed errors, rerun with: -v
==823== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)
Illegal instruction
#
Hm ???
Dave Goodell
13-04-2010 22:28
To
Mogens Lin
dependent on the input data from the internet radio and also timing.
I will see if I can make a testcase to prove your patch.
Thanks!
Best regards,
Mogens
Dave Goodell
13-04-2010 17:39
To
Dave Goodell
cc
valgrind-users@lists.sourceforge.net, Mogens Lindholdt Lauridsen
Subject
Re
Hi,
I got this message from valgrind:
dis_cache_manage(ppc)(opc1|b21to25|b0)
disInstr(ppc): unhandled instruction: 0x7C2907EC
primary 31(0x1F), secondary 2028(0x7EC)
==714== valgrind: Unrecognised instruction at address 0x10d410e0.
==714== Your program just tried to execute an in
: _dl_start (rtld.c:551)
==1012==by 0x40164CF: _start (in /lib/ld-2.5.90.so)
(Which I guess mean valgrind is missing this instruction.)
/Mogens
Brandon Rioja
09-10-2009 23:16
To
Mogens Lindholdt Lauridsen
cc
"valgrind-users@lists.sourceforge.net"
Subject
RE: [Valg
==1012== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 2)
Illegal instruction
From: Mogens Lindholdt Lauridsen [mailto:m...@bang-olufsen.dk]
Sent: Friday, October 09, 2009 4:20 PM
To: Brandon Rioja
Cc: Tom Hughes; valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Mon
o I didn't bother to figure these
setting out. Sorry...)
/Mogens
Brandon Rioja
09-10-2009 17:31
To
Tom Hughes
cc
"valgrind-users@lists.sourceforge.net"
, Mogens Lindholdt Lauridsen
Subject
Re: [Valgrind-users] Montavista cross compilation
After I got valgrind
I build valgrind for PPC using cross compiler like this:
#*
export location=$(pwd)
export
TARGET_TOOL_BASE=/opt/wrsysroot/x86-linux2/powerpc-wrs-linux-gnu-ppc_603e-glibc_small-
export CC=${TARGET_TOOL_BASE}gcc
export CXX=${TARGET_TOOL_BASE}g++
export LD=${TARGET_TOOL_BASE}ld
svn
Interesting..., so what about cross-compiling?
I build valgrind on Suse x86 for PPC32 using a build script like this:
export
CC=/opt/wrsysroot/x86-linux2/powerpc-wrs-linux-gnu-ppc_603e-glibc_small-gcc
export
CXX=/opt/wrsysroot/x86-linux2/powerpc-wrs-linux-gnu-ppc_603e-glibc_s
13 matches
Mail list logo
