Re: [Valgrind-users] Re: invalid file descriptor

[Geoff A. <gal...@nc...>]

----- Original Message -----
From: "Nicholas Nethercote" <nj...@ca...>

Thanks for the update.  I'll try out the the change to the
VG_(pp_ExeContext)() call  the next time I'm on my Linux development
machine.

> As for why you want to suppress it... is there a good reason why you're
> passing -1 as a file descriptor to read()?

The error actually occurs in the execution of a vfscanf() call.  This call
is made in unit test code, in which  I'm passing a closed stream to a
function that makes a vfscanf() call to test the function's error handling
logic.  I'm developing and testing with glibc 2.2.0 and gcc 3.3 on SuSE 7.1.
The vscanf() call does return EOF with an errno of EBADF as expected when
passed the closed stream.  But, in addition to the invalid file descriptor
warning for read(), valgrind reports over 60 other "memory" errors from the
vfscanf() call, which I suppress.  Since this is unit test code, I'll simply
ignore the warning.

Thanks again for the info.

Geoff Alexander