> ==1019== Warning: noted but unhandled ioctl 0xae03 with no size/direction
> hints
> ==1019== This could cause spurious value errors to appear.
> ==1019== See README_MISSING_SYSCALL_OR_IOCTL for guidance on
> writing a proper wrapper.
The syscall is:
ioctl(fd, 0xae03, ...)
where 'fd' is some file descriptor, and the ellipsis '...' means
that there may be more arguments. In most cases, there are three
arguments, and the last one is the address of some 'struct' that
is specific to the "operation code" 0xae03.
Notice that 0==(0xffff0000 & 0xae03) , which means that the operation
code 0xae03 has no direction hints (the 0xc0000000 bits) and also
omits the size hint (the 0x3fff0000 bits.) There are literally
thousands of ioctl opcodes (the 0x0000ffff bits), and knowing the
size and direction of data transfer is a big pain. Therefore
in most cases the size and direction are part of the high 16 bits
of the opcode; but not in this case.
You can try searching /usr/include/.../*.h files for "ae03", but
this is likely to fail because the source for the opcode probably
is something like "(FOO|3)" with a "#define FOO 0xae00".
One good way to learn more is to run the app under 'strace'.
Strace decodes and prints syscalls as they occur. Strace knows
many ioctl already, but perhaps not 0xae03. However, the output from
strace will enable you to find the 'fd' and probably its filename.
Find the syscall with 0xae03 as the second argument, then search
backward for the 'open' whose return value equals the first argument
to the ioctl.
--
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
