Re: [Valgrind-users] Missing ioctl for TIOCEXCL and TIOCNXCL

[Tom H. <to...@co...>]

On 17/03/2019 15:03, Jeffrey Walton wrote:

> Working from Master I got the message about the missing ioctl:
> 
> Debug: term_config
> ==3366== Warning: noted but unhandled ioctl 0x540c with no size/direction hints.
> ==3366==    This could cause spurious value errors to appear.
> ==3366==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper
>   wrapper.
> 
> Following http://www.valgrind.org/docs/manual/dist.readme-missing.html
> I found the source files don't really follow what is described. For
> example, I only see PRE_unknown_ioctl and POST_unknown_ioctl, and I
> don't see the big collection of existing ioctl's as described. I don't
> think it is a good idea to go further (for me).

You're looking for PRE(sys_ioctl) and POST(sys_ioctl) here:

coregrind/m_syswrap/syswrap-linux.c

> Both ioctl's take a NULL argument, so no parameters are passed.

If there's no memory being read or written then the warning
is harmless and you can ignore it.

Tom

-- 
Tom Hughes (to...@co...)
http://compton.nu/