[Valgrind-developers] 2007-12-12 03:15:03 GMT nightly build (alvis, i686, Red Hat 7.3)

Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-12-12 03:15:03 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ..

[Valgrind-developers] 2007-12-12 03:05:08 GMT nightly build (lloyd, x86_64, Fedora 7)

Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2007-12-12 03:05:08 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ...

[Valgrind-developers] 2007-12-12 03:10:05 GMT nightly build (dellow, x86_64, Fedora 8)

Nightly build on dellow ( x86_64, Fedora 8 ) started at 2007-12-12 03:10:05 GMT Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... f

[Valgrind-developers] valgrind: r7298 - in trunk: cachegrind/tests/x86 exp-drd exp-drd/docs exp-drd/tests exp-omega exp-omega/docs exp-omega/tests helgrind helgrind/docs helgrind/tests massif massif/p

Author: rjwalsh Date: 2007-12-12 03:16:52 + (Wed, 12 Dec 2007) New Revision: 7298 Log: Update ignores. Modified: trunk/cachegrind/tests/x86/ trunk/exp-drd/ trunk/exp-drd/docs/ trunk/exp-drd/tests/ trunk/exp-omega/ trunk/exp-omega/docs/ trunk/exp-omega/tests/ trunk/helg

[Valgrind-developers] 2007-12-12 03:00:03 GMT nightly build (gill, x86_64, Fedora Core 2)

Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-12-12 03:00:03 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests

[Valgrind-developers] 2007-12-12 02:00:01 CET nightly build (g5, SuSE 10.1, ppc970)

Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-12-12 02:00:01 CET Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... f

Re: [Valgrind-developers] Assertion valgrinding wine

On Monday 10 December 2007, Dan Kegel wrote: > > it is unfortunately a known problem that -Wstrict-overflow > > does not warn about everything that it exploits for optimisation. > Got a gcc bugzilla number for that? Not really. I have plenty of testcases though. example: void table_init(int* val

Re: [Valgrind-developers] [Valgrind-announce] Valgrind-3.3.0 is available

On Tue, 11 Dec 2007, Julian Seward wrote: > We are pleased to announce a new release of Valgrind, version 3.3.0, > available from http://www.valgrind.org. > [...] > Our thanks to all those who contribute to Valgrind's development. > This release represents a great deal of time, energy and effort o

[Valgrind-developers] Valgrind-3.3.0 is available

We are pleased to announce a new release of Valgrind, version 3.3.0, available from http://www.valgrind.org. Valgrind is an open-source suite of simulation based debugging and profiling tools. With the tools that come with Valgrind, you can automatically detect many memory management and threadi

[Valgrind-developers] Runtime control for valgrind?

Hello, has there been any discussion on implementing something like what is suggested in this article for valgrind? http://www.ddj.com/cpp/204800654 Seems like it wouldn't be too difficult to add something like the following: vallgrind_control --start-leak-check --pid= vallgrind_control -