Re: [Valgrind-developers] Setting fd number used by --log-file?

[Dan S. <dan...@go...>]

On 27 May 2012 01:40, Dan Shelton <dan...@go...> wrote:
> On 27 May 2012 01:29, Philippe Waroquiers <phi...@sk...> wrote:
>> On Sun, 2012-05-27 at 01:20 +0200, Dan Shelton wrote:
>>> Is there a way to set the fd number used by the --log-file number?
>>> We've encountered serious trouble when we test the bash/dash/ksh
>>> family of shells with valgrind, sometimes testing fails because there
>>> are fds used by valgrind which are considered free by the shell.
>> I understand that Valgrind should properly indicate to bash/dash/ksh
>> the fd range which is usable.
>>
>> Valgrind reserves a part of the fd range for its own use.
>> This reserved part should not be visible to the client
>> (i.e. valgrind ensures that the syscall getrlimit
>> returns a range not including the reserved for Valgrind).
>>
>> How is bash/... guessing that they can use such
>> a reserved fd ?
>
> We've guessed that because some of the tests have valgrind output
> inside while we explicitly set --log-file. The best guess was that the
> shell tests which have fd numbers hardcoded interfere with valgrinds
> fd usage. But we might be wrong with that.

Which fd numbers does valgrind typically use on Linux for --log-file?
-- 
Dan Shelton