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
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
The text was updated successfully, but these errors were encountered:
I guess you're in W10, in this case x64dbg labels the function call differently due the ntdll stub code
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
Edit: I guess the same goes for all the other API calls cases you mentioned before
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
The text was updated successfully, but these errors were encountered: