Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2008-01-13 03:05:09 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 dellow ( x86_64, Fedora 8 ) started at 2008-01-13 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
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2008-01-13 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
Author: sewardj
Date: 2008-01-13 01:54:19 + (Sun, 13 Jan 2008)
New Revision: 7340
Log:
Improve .bss handling. I still don't really understand how to
reliably figure out at which VMA ld.so maps the .bss section, though.
Also, handle .sdata segments -- these are another kind of .data
segment t
Author: sewardj
Date: 2008-01-13 01:47:56 + (Sun, 13 Jan 2008)
New Revision: 7339
Log:
Make the argument to VG_(log2) be unsigned. Doesn't really make sense
to interpret it as a signed value.
Modified:
branches/DATASYMS/coregrind/m_libcbase.c
branches/DATASYMS/include/pub_tool_libcbase
On Sunday 13 January 2008, Nicholas Nethercote wrote:
> On Fri, 11 Jan 2008, Josef Weidendorfer wrote:
>
> > An interesting thing for cachegrind/callgrind would be to get global figures
> > on cache events related to data names. This would involve calling
> > VG_(get_dataname_and_offset) for every
On Sun, 13 Jan 2008, Josef Weidendorfer wrote:
>> Would it be possible to run helgrind under callgrind? Did you try gprof? Any
>> other suggestions?
>
> Yes.
> Check out "Self hosting" in README_DEVELOPERS.
>
> To run callgrind on a Valgrind tool, you need to specify
> "--pop-on-jump=yes" for the
On Friday 11 January 2008, Konstantin Serebryany wrote:
> Dear valgrind developers,
>
> How do you usually profile valgrind tools?
>
> I tried to profile a particularly long run of helgrind with oprofile.
> The test runs ~1 second on a real CPU and fails after few hours under
> helgrind.
> The fl
On Fri, 11 Jan 2008, Josef Weidendorfer wrote:
> An interesting thing for cachegrind/callgrind would be to get global figures
> on cache events related to data names. This would involve calling
> VG_(get_dataname_and_offset) for every read/write access, which is a lot of
> overhead.
>
> A solution
