Re: [Valgrind-users] 2.1.0 Syscall error reporting

[Jeremy F. <je...@go...>]

On Fri, 2003-12-26 at 05:37, Steve G wrote:
> OK, we set some descriptors to -1 when they have been previously
> closed and I'd like to find this bug...but there's no location
> information given in the output. No stack trace. Is there a way
> to enable this?

-v.  --track-fds=yes should probably enable this too.

> Another thing that xinetd does on startup is close all file
> descriptors between 2 & FD_SETSIZE or lim_max as returned by
> getrlimit() (or getdtablesize if RLIMIT_NOFILE is not available),
> whichever is lower. The curious things is that valgrind started
> reporting close syscall errors from 821-1023. Where is valgrind
> getting the 821 from?

Valgrind needs to use file descriptors for its own internal use, so it
prevents the client from using a range of descriptors.  HEAD now updates
the soft limit to reflect this (though I don't think it enforces a hard
limit).

	J