valgrind 3.5 on Mac OS X 10.5.8 is giving me this message: ==9399== Warning: noted but unhandled ioctl 0x2000747b with no size/ direction hints ==9399== This could cause spurious value errors to appear. ==9399== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==9399== Warning: noted but unhandled ioctl 0x2000747a with no size/ direction hints ==9399== This could cause spurious value errors to appear. A user on the mailing list provided this useful info: ---- $ grep "'t', 123" */*.h sys/ttycom.h:#define TIOCSBRK _IO('t', 123) /* set break bit */ That is decoded from 0x2000747b as follows: _IO(...) 0x20000000 't' 0x74 123 0x7b Since no data is moving into or out of the kernel (that would use _IOR (...) or _IOW(...) or _IOWR(...) wrapping, its just as easy to ignore the error as anything else. ---- Can this ioctl be 'wrapped' on OS X? I am working on a minimal test case....
The following will trigger the warning in valgrind: int main (int argc, char * const argv[]) { (void)tcsendbreak(1, 0); return 0; }
Resolved in r15246.