|
From: Tom H. <th...@cy...> - 2003-12-17 11:41:49
|
In message <1071540160.20064.65.camel@localhost.localdomain>
Jeremy Fitzhardinge <je...@go...> wrote:
> I've been testing this pretty solidly for a while, so I think it should
> work OK. No doubt you'll find some problems, but that's why I'm
> checking it in (and why we did the 2.1.0 release *before* checking it in
> - so that there's something semi-stable for people to play with).
I've just had a go with the CVS head, and I've found a couple of minor
issues with it:
With RH9 it was complaining about syscall 258 which is set_tid_address
which is called by ld.so early on, so valgrind never used to see it. A
patch to add support for this is attached.
Although simple programs worked, a debug build of one of our main
programs failed to mmap many of the shared objects. I managed to work
round this by adjusting VALGRIND_MAPSIZE in stage2.c to a little
over 300Mb in size. Debug builds of our software are somewhat extreme
in their use of shared libraries - this program had about 150 or so
and they mostly had level 3 DWARF debugging on.
I noticed that if you track FD leaks then both /usr/bin/valgrind and
the client executable are reported as leaks.
Other than that it seems fine so far...
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|