|
From: Tom H. <th...@cy...> - 2003-10-19 15:03:54
|
In message <106...@ix...>
Jeremy Fitzhardinge <je...@go...> wrote:
> This is a large, complex change. I've been testing it pretty
> extensively, but I expect there's still some bugs in there (I found one
> just before checking in). Please sync to CVS HEAD and try it out on
> your favorite programs.
Your commit has finally shown up in the anonymous CVS tree and it
all seems to be fine so far, except that valgrind fails unless you
have a large soft limit on file descriptors, as follows:
audi [~] % valgrind ls
==2035== valgrind: failed to move logfile fd into safe range
==2035== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux.
==2035== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward.
==2035== Using valgrind-20030725, a program supervision framework for x86-linux.
==2035== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward.
valgrind: vg_mylibc.c:1229 (vgPlain_safe_fd): Assertion `newfd > (1024 - (100*2 + 4))' failed.
==2035== at 0x4016E66B: ???
==2035== by 0x4016E66A: ???
==2035== by 0x4016E6C5: ???
==2035== by 0x4016E7B8: ???
Looking at the code this is because the code that sets up the proxy
threads tries to dup descriptors up to a high number but my descriptor
limit was set to 256 by default.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|