-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Windows 10 64bit] PSUTIL 32bit (WOW64) fails to read process name longer than 128 characters #1980
Comments
If you understand the problem and have a solution for it please attach a diff, but FYI I'm cautious about making changes to that part of the code (WoW 64 process handling). Historically it has always been quite complicated and messy. We had tons of bug reports related to |
@giampaolo PR #1981 is ready. Do you have any timetable to review, test and finish it? |
Summary
Description
PSUTIL 32b fails to read path longer than 128characters due to different behaviour of NtQuerySystemInformation when called by 32bit process (WOW64) in Windows 10 64b. When the NtQuerySystemInformation is called by 32bit process (WOW64) it does not return processIdInfo.ImageName.MaximumLength increased and returns 0x100 (original value), so your library fails on error STATUS_INFO_LENGTH_MISMATCH (24). 64b version of an app gets the processIdInfo.ImageName.MaximumLength correctly increased.
I propose to increase size of the buffer in the iterative way till the API stops sending STATUS_INFO_LENGTH_MISMATCH instead as a workaround to this issue.
See parent issue with reproduction info:
Azure/azure-cli#19193
Please fix, thx.
The text was updated successfully, but these errors were encountered: