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

DefWindowProc doesnt resolve correctly #32

Open
mrfearless opened this issue Apr 21, 2018 · 3 comments
Open

DefWindowProc doesnt resolve correctly #32

mrfearless opened this issue Apr 21, 2018 · 3 comments

Comments

@mrfearless
Copy link

The DefWindowProc defintion in the user32.api def files doesnt pick up this defintion, but just shows as Arg4, Arg3, Arg2, Arg1, DefWindowProcA instead.

Think i seen similar behaviour with couple other apis, cant recall which ones of the top of my head (maybe CallWindowProc) meant to mention this a while back but forgot to do so

@ThunderCls
Copy link
Owner

ThunderCls commented Apr 21, 2018

I guess you're in W10, in this case x64dbg labels the function call differently due the ntdll stub code

image

image

And as there's no definition for NtdllDefWindowProc_A in this case xAnalyzer will use default arguments (Arg4, Arg3, etc). On the other hand you can see how it does get it right in W7 for instance

image

image

Edit: I guess the same goes for all the other API calls cases you mentioned before

@mrfearless
Copy link
Author

Strange, im using Windows 7 64bit. Anyhow its not a big issue, ill try a few more things to see if i can figure out why its that way.

@ThunderCls
Copy link
Owner

My bad xD...I meant x64 version

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

2 participants