|
From: Paul F. <pa...@fr...> - 2009-08-20 15:25:06
|
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 (RHEL3), but test
on RHEL3, 4 and a bit on RHEL5 and SUSE. To pick up the appropriate glibc
suppression file, I do something like
GLIBCMINOR=$(nawk \'/#define.*__GLIBC_MINOR__/{print $3}\'
/usr/include/features.h)
VGAPP=$(which valgrind)
VGDIR=$(dirname $VGAPP)
VGBASEDIR=$(dirname $VGDIR)
export VALGRIND_OPTS="$VALGRIND_OPTS
--suppressions=$VGBASEDIR/lib/valgrind/glibc-2.${GLIBCMINOR}.supp"
Of course, we can still manually copy the suppression files.
A+
Paul
--
Paul Floyd http://paulf.free.fr
|
|
From: Nikos C. <re...@ar...> - 2009-08-20 17:20:22
|
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. We build valgrind on the oldest OS that we support (RHEL3), but test
> on RHEL3, 4 and a bit on RHEL5 and SUSE. To pick up the appropriate glibc
> suppression file, I do something like
>
> GLIBCMINOR=$(nawk \'/#define.*__GLIBC_MINOR__/{print $3}\'
> /usr/include/features.h)
> VGAPP=$(which valgrind)
> VGDIR=$(dirname $VGAPP)
> VGBASEDIR=$(dirname $VGDIR)
> export VALGRIND_OPTS="$VALGRIND_OPTS
> --suppressions=$VGBASEDIR/lib/valgrind/glibc-2.${GLIBCMINOR}.supp"
>
> Of course, we can still manually copy the suppression files.
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 suppression (*.supp) files were
installed. Now, only default.supp is installed. This should not
affect users as the other installed suppression files were not
read; the fact that they were installed was a mistake."
|
|
From: Paul F. <pa...@fr...> - 2009-08-20 21:10:11
|
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 suppression (*.supp) files were > installed. Now, only default.supp is installed. This should not > affect users as the other installed suppression files were not > read; the fact that they were installed was a mistake." I did skim through the release notes, but that paragraph didn't catch my attention. Does this mean that building Valgrind on one OS, installing it on an NFS mount and using it from later OSes isn't really supported? A+ Paul -- Paul Floyd http://paulf.free.fr |
|
From: Julian S. <js...@ac...> - 2009-08-20 21:39:04
|
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 > > note said: > > > > "- Previously, all the distributed suppression (*.supp) files were > > installed. Now, only default.supp is installed. This should not > > affect users as the other installed suppression files were not > > read; the fact that they were installed was a mistake." > > I did skim through the release notes, but that paragraph didn't catch my > attention. > > Does this mean that building Valgrind on one OS, installing it on an NFS > mount and using it from later OSes isn't really supported? It's not supported. The build system assumes that the build is done for one platform (distro) only. If you need to run it on multiple distros, you really should build it individually for each distro. In some circumstances you might get away with using a build from one distro on a different one, but if that works it's more by accident than design. J |
|
From: Mogens L. L. <ML...@ba...> - 2009-08-20 22:17:48
|
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_small-g++
export
LD=/opt/wrsysroot/x86-linux2/powerpc-wrs-linux-gnu-ppc_603e-glibc_small-ld
export LDFLAGS=-L/home/mln/evb/rootfs/usr/lib
tar -xjf valgrind-3.3.1_with_mfspr_patch.tar.bz2
cd valgrind-3.3.1
./configure --prefix=/home/mln/valgrind/install_debug
--enable-shared --host=ppc-linux --target=ppc-linux --enable-debug
--disable-tls || exit 1
make || exit 1
make install || exit 1
Will this give me the correct suppression files?
Another thing:
As you may see in the script above I use mfspr patch. I had problems
running valgrind on PPC, since it reported illegal instruction. I have
added support for this instruction (which reads the CPU Core id/type). I
have mailed this patch to this list in 18 June 2009 (Re: [Valgrind-users]
PPC: unhandled instruction: dis_proc_ctl(ppc)(mfspr, SPR)(0x11F)), but
didn't really get any feedback. See :
http://sourceforge.net/mailarchive/message.php?msg_name=B54FB955F5DC4DF1826FD76E9CB943A7%40mail2world.com
Could this be added to the repository?
Kind regards,
Mogens
Julian Seward <js...@ac...>
20-08-2009 23:41
To
val...@li...
cc
Subject
Re: [Valgrind-users] suppression files with valgrind 3.5.0
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
> > note said:
> >
> > "- Previously, all the distributed suppression (*.supp) files were
> > installed. Now, only default.supp is installed. This should not
> > affect users as the other installed suppression files were not
> > read; the fact that they were installed was a mistake."
>
> I did skim through the release notes, but that paragraph didn't catch my
> attention.
>
> Does this mean that building Valgrind on one OS, installing it on an NFS
> mount and using it from later OSes isn't really supported?
It's not supported. The build system assumes that the build is done for
one platform (distro) only. If you need to run it on multiple distros,
you really should build it individually for each distro.
In some circumstances you might get away with using a build from one
distro on a different one, but if that works it's more by accident than
design.
J
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Valgrind-users mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users
|
|
From: Bart V. A. <bar...@gm...> - 2009-08-23 08:41:41
|
On Fri, Aug 21, 2009 at 12:02 AM, Mogens Lindholdt Lauridsen<ML...@ba...> wrote: > > 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_small-g++ > export > LD=/opt/wrsysroot/x86-linux2/powerpc-wrs-linux-gnu-ppc_603e-glibc_small-ld > > > export LDFLAGS=-L/home/mln/evb/rootfs/usr/lib > > tar -xjf valgrind-3.3.1_with_mfspr_patch.tar.bz2 > cd valgrind-3.3.1 > ./configure --prefix=/home/mln/valgrind/install_debug > --enable-shared --host=ppc-linux --target=ppc-linux --enable-debug > --disable-tls || exit 1 > make || exit 1 > make install || exit 1 > > Will this give me the correct suppression files? Cross-compilation was broken in 3.3.0 but works fine with 3.4.0 and 3.4.1 and should still work fine with 3.5.0 (see also https://bugs.kde.org/show_bug.cgi?id=162295). Bart. |
|
From: Bart V. A. <bar...@gm...> - 2009-08-23 08:58:15
|
On Sun, Aug 23, 2009 at 10:41 AM, Bart Van Assche<bar...@gm...> wrote: > On Fri, Aug 21, 2009 at 12:02 AM, Mogens Lindholdt > Lauridsen<ML...@ba...> wrote: >> >> Interesting..., so what about cross-compiling? > > Cross-compilation was broken in 3.3.0 but works fine with 3.4.0 and > 3.4.1 and should still work fine with 3.5.0 (see also > https://bugs.kde.org/show_bug.cgi?id=162295). Update: cross-compilation is broken again in 3.5.0 -- see also https://bugs.kde.org/show_bug.cgi?id=204843. I assume that a fix will be included in 3.5.1. Bart. |
|
From: Bart V. A. <bar...@gm...> - 2009-08-29 06:13:40
|
On Sun, Aug 23, 2009 at 10:58 AM, Bart Van Assche<bar...@gm...> wrote: > On Sun, Aug 23, 2009 at 10:41 AM, Bart Van > Assche<bar...@gm...> wrote: >> On Fri, Aug 21, 2009 at 12:02 AM, Mogens Lindholdt >> Lauridsen<ML...@ba...> wrote: >>> >>> Interesting..., so what about cross-compiling? >> >> Cross-compilation was broken in 3.3.0 but works fine with 3.4.0 and >> 3.4.1 and should still work fine with 3.5.0 (see also >> https://bugs.kde.org/show_bug.cgi?id=162295). > > Update: cross-compilation is broken again in 3.5.0 -- see also > https://bugs.kde.org/show_bug.cgi?id=204843. I assume that a fix will > be included in 3.5.1. Another update: a fix is available both on the trunk and on the Valgrind 3.5.x branch that makes cross-compilation again possible. Bart. |