Re: [Valgrind-users] Handling ioctl 0x30000001 in valgrind?

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

On 31/01/15 15:07, Carl Ponder wrote:

> Grep'ing through the files in these directories
>
>     /usr/src/
>     /usr/include
>     /shared/apps/cuda/CUDA-v7.0.18
>     /shared/apps/rhel-6.2/tools/$USER/ValGrind-3.10.1
>
> I can't find anything that maps the address 30000001.
> Are these mappings only present for syscalls but not ioctl's?
> Or do we need to install a development version of the /usr/src files?

Well you won't normally find a raw ioctl number in the source because 
they are normally constructed with the _IO. _IOR, _IOW or _IOWR macros.

Specifically, and assuming this is amd64-linux, that number appears to 
correspond to:

   _IO(0x3000, 1)

But in all honest, given you presumably have the source to libcuda, the 
easiest thing will be just to look at that source to see what the ioctl 
is that is being called!

Tom

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