|
From: Ferro, A. <Ala...@me...> - 2007-07-11 14:12:52
|
All,=20
I'm trying to update a suppression file, for a new version of our
codebase. I want to ignore all errors coming from the TCL libraries, as
these are not developed by us. Therefore I added the following
suppression to my standard suppression file:
{=20
tcl84_libtcl8.4.so=20
Memcheck:Addr4=20
obj:/path1/ActiveTcl8.4.12/Linux_i386/lib/libtcl8.4.so=20
obj:/path2/ActiveTcl8.4.12/Linux_i386/lib/libtcl8.4.so=20
}=20
However I find that this doesn't work - I get all the errors. If I split
the suppression into two:=20
{=20
tcl84_libtcl8.4.so=20
Memcheck:Addr4=20
obj:/path1/ActiveTcl8.4.12/Linux_i386/lib/libtcl8.4.so=20
}=20
{=20
tcl84_libtcl8.4.so=20
Memcheck:Addr4=20
obj:/path2/ActiveTcl8.4.12/Linux_i386/lib/libtcl8.4.so=20
}=20
Then it correctly suppresses all the errors from TCL.=20
I'm using valgrind 3.2.3, compiled by hand on RHEL4 (dual core Core2).=20
Is this a bug or does valgrind not support naming multiple objects in a
single suppression?=20
Thanks,=20
Alasdair.=20
|
|
From: Nicholas N. <nj...@cs...> - 2007-07-11 21:52:24
|
On Wed, 11 Jul 2007, Ferro, Alasdair wrote: > Is this a bug or does valgrind not support naming multiple objects in a > single suppression? The latter. Each suppression specifies a single (modulo wildcards) stack trace. Nick |
|
From: Ferro, A. <Ala...@me...> - 2007-07-12 07:48:55
|
Thanks for the quick reply. I had misunderstood the documentation
(snippet below). The list of object files is infact a stack "trace",
rather than being a listed of possible sources, which is what I,
mistakenly, read it as.
Thanks for your help,
Alasdair
In section 2.5 of the Core Manual:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~
{
libX11.so.6.2/libX11.so.6.2/libXaw.so.7.0
Memcheck:Value4
obj:/usr/X11R6/lib/libX11.so.6.2
obj:/usr/X11R6/lib/libX11.so.6.2
obj:/usr/X11R6/lib/libXaw.so.7.0
}
Suppress any size 4 uninitialised-value error which occurs anywhere in
libX11.so.6.2, when called from anywhere in the same library, when
called from anywhere in libXaw.so.7.0. The inexact specification of
locations is regrettable, but is about all you can hope for, given that
the X11 libraries shipped with Red Hat 7.2 have had their symbol tables
removed.=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~
-----Original Message-----
From: Nicholas Nethercote [mailto:nj...@cs...]=20
Sent: 11 July 2007 22:52
To: Ferro, Alasdair
Cc: val...@li...
Subject: Re: [Valgrind-users] Suppression File
On Wed, 11 Jul 2007, Ferro, Alasdair wrote:
> Is this a bug or does valgrind not support naming multiple objects in=20
> a single suppression?
The latter. Each suppression specifies a single (modulo wildcards)
stack trace.
Nick
|