You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On W7 x64 the SizeOfHelperData is 4 and all the bytes after the remote address are initialized (on the issue #421 test).
On XP 32 (and maybe 64-bit too) the SizeOfHelperData is more (104 on 32-bit) and some data in the middle is uninit.
The current comment in drmemory/syscall_windows.c says:
/* XXX: helper data could be a struct w/ padding. I have seen pieces of
* it be uninit on XP. If see many false positives here should just
* disable this until understand its structure.
*/
btw, it's possible that helper data doesn't contain any data originating from the winsock client (i.e. a user program), so false negatives may not very important.
After looking briefly at the ReactOS sources I had an impression that HELPER_DATA structure contains only stuff like refcount and function pointers (callbacks) - something that a mortal winsock user should not work with.
From timurrrr@google.com on May 30, 2011 04:33:39
On W7 x64 the SizeOfHelperData is 4 and all the bytes after the remote address are initialized (on the issue #421 test).
On XP 32 (and maybe 64-bit too) the SizeOfHelperData is more (104 on 32-bit) and some data in the middle is uninit.
The current comment in drmemory/syscall_windows.c says:
/* XXX: helper data could be a struct w/ padding. I have seen pieces of
* it be uninit on XP. If see many false positives here should just
* disable this until understand its structure.
*/
xref issue #375
Original issue: http://code.google.com/p/drmemory/issues/detail?id=424
The text was updated successfully, but these errors were encountered: