Re: [Valgrind-users] suppression files with valgrind 3.5.0

2009-08-20 Thread Mogens Lindholdt Lauridsen
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

Re: [Valgrind-users] suppression files with valgrind 3.5.0

2009-08-20 Thread Julian Seward
On Thursday 20 August 2009, Paul Floyd wrote: > Nikos Chantziaras wrote: > > If you look at the release notes of 3.5.0 (they were posted here too) > > you'll see that this change is intended. So if you want the extra > > suppression files, you will need to copy them manually. The specific > > not

Re: [Valgrind-users] suppression files with valgrind 3.5.0

2009-08-20 Thread Paul Floyd
Nikos Chantziaras wrote: > > If you look at the release notes of 3.5.0 (they were posted here too) > you'll see that this change is intended. So if you want the extra > suppression files, you will need to copy them manually. The specific > note said: > > "- Previously, all the distributed s

Re: [Valgrind-users] suppression files with valgrind 3.5.0

2009-08-20 Thread Nikos Chantziaras
On 08/20/2009 06:24 PM, Paul Floyd wrote: > Hi > > I just built and installed Valgrind 3.5.0. When I did this, I noticed that all > of the suppression files no longer get installed, just default.supp. I suppose > that this is OK in a single machine environment, but for us it is a small > regression

[Valgrind-users] suppression files with valgrind 3.5.0

2009-08-20 Thread Paul Floyd
Hi I just built and installed Valgrind 3.5.0. When I did this, I noticed that all of the suppression files no longer get installed, just default.supp. I suppose that this is OK in a single machine environment, but for us it is a small regression. We build valgrind on the oldest OS that we support

Re: [Valgrind-users] Patch for "vex x86->IR: unhandled instruction bytes: 0xF 0xE 0x89 0xE6"

2009-08-20 Thread Nicholas Nethercote
On Thu, Aug 20, 2009 at 8:35 PM, Sven Buijssen wrote: > > Revision 1604 patched VEX/priv/guest_amd64_toIR.c (so it fixed the problem > when > using 64bit Goto BLAS), but not VEX/priv/guest_x86_toIR.c. Ah, thanks for the clarification. Can you please file a bug report so this doesn't get lost? (h

Re: [Valgrind-users] Patch for "vex x86->IR: unhandled instruction bytes: 0xF 0xE 0x89 0xE6"

2009-08-20 Thread Sven Buijssen
Hi Nick, >> I'd like to provide a patch for VEX/priv/guest_x86_toIR.c such that running >> user >> code that uses a 32-bit Goto BLAS library through memcheck (from the valgrind >> 3.5.0 release or earlier releases) does not issue a >> >>> vex x86->IR: unhandled instruction bytes: 0xF 0xE 0x89 0xE

Re: [Valgrind-users] Patch for "vex x86->IR: unhandled instruction bytes: 0xF 0xE 0x89 0xE6"

2009-08-20 Thread Nicholas Nethercote
On Thu, Aug 20, 2009 at 7:25 PM, Sven Buijssen wrote: > > I'd like to provide a patch for VEX/priv/guest_x86_toIR.c such that running > user > code that uses a 32-bit Goto BLAS library through memcheck (from the valgrind > 3.5.0 release or earlier releases) does not issue a > >> vex x86->IR: unhan

[Valgrind-users] Patch for "vex x86->IR: unhandled instruction bytes: 0xF 0xE 0x89 0xE6"

2009-08-20 Thread Sven Buijssen
Hi, I'd like to provide a patch for VEX/priv/guest_x86_toIR.c such that running user code that uses a 32-bit Goto BLAS library through memcheck (from the valgrind 3.5.0 release or earlier releases) does not issue a > vex x86->IR: unhandled instruction bytes: 0xF 0xE 0x89 0xE6 > ==29436== valgrind