Skip to content
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

handling 64-bit windows app system calls #945

Open
derekbruening opened this issue Nov 28, 2014 · 3 comments
Open

handling 64-bit windows app system calls #945

derekbruening opened this issue Nov 28, 2014 · 3 comments

Comments

@derekbruening
Copy link
Contributor

From bruen...@google.com on July 19, 2012 14:10:48

should be able to just use the wow64 #s but may want to verify there are no
differences in args that the wow64 marshaling hides

note that:

  • XXX: imm32 on x64 seems to have a complete set of user32 wrappers!
  • for now not looking at x64 imm32 but may need to eventually do automated
  • cross-dll de-duplication.

Original issue: http://code.google.com/p/drmemory/issues/detail?id=945

@derekbruening
Copy link
Contributor Author

From bruen...@google.com on July 23, 2012 07:12:20

one issue is that my syscall tables store the arg count as a size on the
stack, but on x64 the pointers are larger and the calling convention is
different. for short-term the code should be changed to divide by 4, not
sizeof(reg_t), to get the count.

@derekbruening
Copy link
Contributor Author

From bruen...@google.com on February 17, 2013 10:20:50

the arg count was fixed in r1020 . that just leaves "verify there are no
differences in args that the wow64 marshaling hides", and imm32.

@derekbruening
Copy link
Contributor Author

From bruen...@google.com on September 18, 2014 07:41:35

Issue 919 has been merged into this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant