[Valgrind-developers] 2007-12-31 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-31 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-31 03:05:13 GMT nightly build (lloyd, x86_64, Fedora 7)

Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2007-12-31 03:05:13 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-31 03:10:04 GMT nightly build (dellow, x86_64, Fedora 8)

Nightly build on dellow ( x86_64, Fedora 8 ) started at 2007-12-31 03:10:04 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] 2007-12-31 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-31 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

Re: [Valgrind-developers] Proposal: ensure that VG_(running_tid) != VG_INVALID_THREADID for all client memory accesses

On 20/12/2007, Bart Van Assche <[EMAIL PROTECTED]> wrote: > There is a small inconsistency in the Valgrind core with regard to the > value of VG_(running_tid) concerning client memory accesses: this > variable contains a valid thread ID for all client memory accesses, > except for some accesses tr

Re: [Valgrind-developers] Proposal: do not require inclusion of when including

On 27/12/2007, Bart Van Assche <[EMAIL PROTECTED]> wrote: > The include file contains declarations for various > libc-functions. Two of these functions (VG_(getrlimit)() and > VG_(setrlimit)()) accept a pointer to a vki_rlimit structure. Inclusion of > pub_tool_vki.h is now required even when nei

Re: [Valgrind-developers] Proposal: add const keyword to OSet declarations where appropriate

On 27/12/2007, Bart Van Assche <[EMAIL PROTECTED]> wrote: > I know that not everyone uses the const keyword wherever possible, but I > would appreciate if the Valgrind core would support programmers that follow > this style. Currently it is not possible to pass pointers to const keys to > the OSet

[Valgrind-developers] valgrind: r7308 - in trunk: cachegrind coregrind include

Author: tom Date: 2007-12-30 12:28:26 + (Sun, 30 Dec 2007) New Revision: 7308 Log: Add const qualifiers to appropriate arguments of OSet routines. Patch from Bart Van Assche <[EMAIL PROTECTED]>. Modified: trunk/cachegrind/cg_main.c trunk/coregrind/m_oset.c trunk/include/pub_tool_ose