> Maybe I should have made myself more clear. The comment in
> tests/vg_regtest.pl.in explains that stdout.exp files only can have a
> numeric suffix ([0-9]*), while stderr.exp files can have any suffix
> (*). If I understood the tests/vg_regtest.pl.in sourcecode correctly,
> both stdout.exp and s
On Wednesday 27 February 2008 08:18, Bart Van Assche wrote:
> On Tue, Feb 26, 2008 at 8:51 PM, Julian Seward <[EMAIL PROTECTED]> wrote:
> > On Tuesday 26 February 2008 20:36, Bart Van Assche wrote:
> > > The result of the regression test helgrind/tests/tc20_verifywrap
> > > depends on the platfo
On Wed, Feb 27, 2008 at 11:49 AM, Julian Seward <[EMAIL PROTECTED]> wrote:
>
> > Maybe I should have made myself more clear. The comment in
> > tests/vg_regtest.pl.in explains that stdout.exp files only can have a
> > numeric suffix ([0-9]*), while stderr.exp files can have any suffix
> > (*).
On Wed, 2008-02-27 at 11:49 +0100, Julian Seward wrote:
> > Maybe I should have made myself more clear. The comment in
> > tests/vg_regtest.pl.in explains that stdout.exp files only can have a
> > numeric suffix ([0-9]*), while stderr.exp files can have any suffix
> > (*). If I understood the test
My $0.02
In my variant of helgrind I have a client request saying that we
expect a race on a particular address.
If the race is detected, the tool is silent. But if the race is *not*
detected, the tool complains at the end.
This is not a substitute for the current testing scheme; it is quite
ortho
Author: bart
Date: 2008-02-27 15:38:10 + (Wed, 27 Feb 2008)
New Revision: 7488
Log:
Make sure tc20_verifywrap does not trigger an assertion failure in combination
with glibc 2.7.
Modified:
trunk/helgrind/tests/tc20_verifywrap.c
Modified: trunk/helgrind/tests/tc20_verifywrap.c
==
Author: bart
Date: 2008-02-27 15:46:00 + (Wed, 27 Feb 2008)
New Revision: 7489
Log:
Modified drd client requests such that the mutex type can be passed from the
intercepts to the tool. An error message is now printed in case a locked mutex
is destroyed and in case a thread exits while it hol
Author: bart
Date: 2008-02-27 16:13:05 + (Wed, 27 Feb 2008)
New Revision: 7490
Log:
An error message is now printed before attempting to lock a non-recursive mutex
recursively.
Added:
trunk/exp-drd/tests/recursive_mutex.stderr.exp
trunk/exp-drd/tests/recursive_mutex.stdout.exp
trunk
Author: bart
Date: 2008-02-27 17:42:04 + (Wed, 27 Feb 2008)
New Revision: 7492
Log:
Converted to new mutex error message format.
Modified:
trunk/exp-drd/tests/tc20_verifywrap.stderr.exp2
trunk/exp-drd/tests/tc22_exit_w_lock.stderr.exp-64bit
Modified: trunk/exp-drd/tests/tc20_verifywra
Author: bart
Date: 2008-02-27 17:41:22 + (Wed, 27 Feb 2008)
New Revision: 7491
Log:
Fixed compiler warning.
Modified:
trunk/exp-drd/tests/recursive_mutex.c
Modified: trunk/exp-drd/tests/recursive_mutex.c
===
--- trunk/exp-dr
Author: bart
Date: 2008-02-27 18:06:09 + (Wed, 27 Feb 2008)
New Revision: 7493
Log:
Updated to do list.
Modified:
trunk/exp-drd/TODO.txt
Modified: trunk/exp-drd/TODO.txt
===
--- trunk/exp-drd/TODO.txt 2008-02-27 17:42:0
Author: njn
Date: 2008-02-27 18:10:19 + (Wed, 27 Feb 2008)
New Revision: 7494
Log:
Make comments reflect the code.
Modified:
trunk/tests/vg_regtest.in
Modified: trunk/tests/vg_regtest.in
===
--- trunk/tests/vg_regtest.in
On Wed, 27 Feb 2008, Bart Van Assche wrote:
> Maybe I should have made myself more clear. The comment in
> tests/vg_regtest.pl.in explains that stdout.exp files only can have a
> numeric suffix ([0-9]*), while stderr.exp files can have any suffix
> (*). If I understood the tests/vg_regtest.pl.in s
On Wed, 27 Feb 2008, Konstantin Serebryany wrote:
> My $0.02
> In my variant of helgrind I have a client request saying that we
> expect a race on a particular address.
> If the race is detected, the tool is silent. But if the race is *not*
> detected, the tool complains at the end.
>
> This is no
Author: sewardj
Date: 2008-02-28 01:36:38 + (Thu, 28 Feb 2008)
New Revision: 7495
Log:
Stop gcc inlining in varinfo5so.c so as to get consistent results --
different gccs inline differently :-(
Modified:
branches/DATASYMS/memcheck/tests/varinfo5.stderr.exp
branches/DATASYMS/memcheck/t
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2008-02-28 03:00:03
GMT
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... failed
Last 20 lines of verbose log follow
Nightly build on trojan ( x86_64, Fedora Core 6 ) started at 2008-02-28
03:25:15 GMT
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests
Nightly build on aston ( x86_64, Fedora Core 5 ) started at 2008-02-28 03:20:12
GMT
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests
Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2008-02-28 03:05:05 GMT
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... fa
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2008-02-28 03:15:08 GMT
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... failed
Last 20 lines of verbose log follow echo
Author: bart
Date: 2008-02-28 07:36:04 + (Thu, 28 Feb 2008)
New Revision: 7496
Log:
Should compile again with linuxthreads header files.
Modified:
trunk/exp-drd/drd_intercepts.c
Modified: trunk/exp-drd/drd_intercepts.c
===
-
21 matches
Mail list logo
