-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add handling for rest of winsock IOCTL codes #377
Comments
From [email protected] on May 12, 2011 08:11:47 r289 added handling for: |
From [email protected] on June 03, 2011 09:04:05 On "ping.exe www.google.com": |
From [email protected] on June 10, 2011 05:33:10 More ioctls: ping.exe: Summary: add handling for rest of winsock IOCTL codes |
From [email protected] on February 17, 2013 09:40:43 Labels: GoodContrib |
From [email protected] on February 17, 2013 10:18:15 Owner: --- |
From [email protected] on May 04, 2011 14:07:48
issue #359 added these:
IOCTL_AFD_GET_INFO: { /* 0x1207b /
IOCTL_AFD_SET_INFO: { / 0x1203b /
IOCTL_AFD_SET_CONTEXT: { / 0x12047 /
IOCTL_AFD_BIND: { / 0x12003 /
IOCTL_AFD_CONNECT: { / 0x12007 /
IOCTL_AFD_DISCONNECT: { / 0x1202b /
IOCTL_AFD_DEFER_ACCEPT: { / 0x120bf /
IOCTL_AFD_RECV: { / 0x12017 /
IOCTL_AFD_SEND: { / 0x1201f /
IOCTL_AFD_EVENT_SELECT: { / 0x12087 */
xref issue #375 and issue #376 in a full net_unittests run I also see these that need to be handled:
10 WARNING: unknown ioctl 0x1200b => op 2
11 WARNING: unknown ioctl 0x12010 => op 4
5 WARNING: unknown ioctl 0x1201b => op 6
3 WARNING: unknown ioctl 0x12023 => op 8
13 WARNING: unknown ioctl 0x12024 => op 9
11 WARNING: unknown ioctl 0x12037 => op 13
230 WARNING: unknown ioctl 0x1208b => op 34
438 WARNING: unknown ioctl 0x120bf => op 47
6 WARNING: unknown ioctl 0x39000e => op 3
17 WARNING: unknown ioctl 0x390012 => op 4
4 WARNING: unknown ioctl 0x390402 => op 256
8 WARNING: unknown ioctl 0x6d0008 => op 2
14 WARNING: unknown ioctl 0x6d0034 => op 13
Original issue: http://code.google.com/p/drmemory/issues/detail?id=377
The text was updated successfully, but these errors were encountered: