Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-12-04 03:15:02 GMT
Results unchanged 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 2007-12-04 03:05:05 GMT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ...
Author: njn
Date: 2007-12-04 03:27:40 + (Tue, 04 Dec 2007)
New Revision: 7271
Log:
tweak message
Modified:
trunk/massif/ms_main.c
Modified: trunk/massif/ms_main.c
===
--- trunk/massif/ms_main.c 2007-12-04 03:15:23 UTC (
Nightly build on dellow ( x86_64, Fedora 8 ) started at 2007-12-04 03:10:04 GMT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ..
Author: njn
Date: 2007-12-04 03:15:23 + (Tue, 04 Dec 2007)
New Revision: 7270
Log:
Two changes:
- Be more robust in the face of malformed stack traces. This avoids some
potential assertion errors (which have affected prior versions of Massif),
but unfortunately reduces the amount of sanit
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-12-04 03:00:02
GMT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests
On Monday 03 December 2007 20:29, Dave Nomura wrote:
> So you tracked down these unitialized values down to the strxxx
> functions defined in ld.so and Valgrind normally intercepts these calls
> because Memcheck can't handle the sorts of code that is generated for
> these routines?
Correct.
> Is
Hi Josef
> attached is a documentation-only patch for callgrind against trunk,
> as committing to trunk is deprecated at the moment. This was noted
> today while answering the bug report 153335.
That seems fine. Please commit.
J
On Monday 03 December 2007 21:37, Dirk Mueller wrote:
> On Monday 03 December 2007, Julian Seward wrote:
> > Please test it on platforms that are important to you, and let me know
> > of any problems (and successes!). If no serious problems show up,
> > 3.3.0 final will be available in about a wee
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-12-04 02:00:01 CET
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... fail
On Monday 03 December 2007, Julian Seward wrote:
> The repo's trunk is now in a freeze state until the final release.
> Please don't commit anything in trunk until then. As is usual,
> at the point of the final release, a 3_3_0_BRANCH will be created
> and the trunk will be unfrozen.
Hi Julian,
On Mon, 3 Dec 2007, Julian Seward wrote:
A release candidate for Valgrind 3.3.0 (3.3.0.RC1) is available for
testing from
http://www.valgrind.org/downloads/valgrind-3.3.0.RC1.tar.bz2
(MD5 = 31936ca686f9daaf094df437b4952ec6).
Please test it on platforms that are important to you, and let me kno
Author: njn
Date: 2007-12-03 21:29:22 + (Mon, 03 Dec 2007)
New Revision: 7269
Log:
Comment-only change.
Modified:
trunk/massif/ms_main.c
Modified: trunk/massif/ms_main.c
===
--- trunk/massif/ms_main.c 2007-12-02 22:15:3
On Mon, 3 Dec 2007, Dirk Mueller wrote:
>> Please test it on platforms that are important to you, and let me know
>> of any problems (and successes!). If no serious problems show up,
>> 3.3.0 final will be available in about a week from now.
>
> the patch below does no longer apply. it is in the
On Monday 03 December 2007, Julian Seward wrote:
> Please test it on platforms that are important to you, and let me know
> of any problems (and successes!). If no serious problems show up,
> 3.3.0 final will be available in about a week from now.
the patch below does no longer apply. it is in t
So you tracked down these unitialized values down to the strxxx
functions defined in ld.so and Valgrind normally intercepts these calls
because Memcheck can't handle the sorts of code that is generated for
these routines? Is it possible to teach Memcheck to deal with these
optimizations?
Stev
On Dec 3, 2007 11:17 AM, Julian Seward <[EMAIL PROTECTED]> wrote:
> Please test it on platforms that are important to you, and let me know
> of any problems (and successes!). If no serious problems show up,
> 3.3.0 final will be available in about a week from now.
Looks OK on Fedora 8 to me.
Sh
In message <[EMAIL PROTECTED]>
Julian Seward <[EMAIL PROTECTED]> wrote:
>> My machines actually check the script out of the repository each
>> night, so just updating the repository to run both would fix my
>> machines.
>
> That's neat. So the top level cron command runs some other little
On Mon, 2007-12-03 at 12:17 +0100, Julian Seward wrote:
> Please test it on platforms that are important to you, and let me know
> of any problems (and successes!). If no serious problems show up,
> 3.3.0 final will be available in about a week from now.
I've unfortunately had minimal time for
On Monday 03 December 2007 09:47, Tom Hughes wrote:
> In message <[EMAIL PROTECTED]>
>
> Nicholas Nethercote <[EMAIL PROTECTED]> wrote:
> > I can either change the script to run 'make exp-regtest' -- which will
> > require Tom and Julian to update their copy of the script on those
> > machi
Greetings.
A release candidate for Valgrind 3.3.0 (3.3.0.RC1) is available for
testing from
http://www.valgrind.org/downloads/valgrind-3.3.0.RC1.tar.bz2
(MD5 = 31936ca686f9daaf094df437b4952ec6).
There are many improvements listed in the NEWS file. A summary:
- Helgrind works again
- Massif
In message <[EMAIL PROTECTED]>
Nicholas Nethercote <[EMAIL PROTECTED]> wrote:
> I can either change the script to run 'make exp-regtest' -- which will
> require Tom and Julian to update their copy of the script on those machines
> -- or we can change 'make regtest' run all of them. I'm
On Fri, 30 Nov 2007, Bart Van Assche wrote:
> Regarding the 3.3.0 release, a question about the nightly build: from
> the nightly build output I can see that the exp-drd source code and
> regression tests are compiled, but are the exp-drd regression tests
> run during the nightly build ? I could n
23 matches
Mail list logo
