https://bugs.winehq.org/show_bug.cgi?id=50405
--- Comment #7 from Samuel Venable samuelvenable@hotmail.com --- (In reply to Samuel Venable from comment #6)
(In reply to Anastasius Focht from comment #2)
Hello Samuel,
you're most likely doing something wrong. There are many libraries/frameworks/applications using that "undocumented" approach. Also you didn't tell if you're running a WoW64 environment which has some restrictions (32-bit -> 64-bit process).
https://stackoverflow.com/questions/7446887/get-command-line-string-of-64- bit-process-from-32-bit-process
'PhGetProcessPebString':
https://github.com/processhacker/processhacker/blob/ 04f18ea9a98374fb5aa4fc0d8c51b93a708eafc4/phlib/native.c#L580
'PhGetProcessCommandLine':
https://github.com/processhacker/processhacker/blob/ 04f18ea9a98374fb5aa4fc0d8c51b93a708eafc4/phlib/native.c#L733
'PhGetProcessEnvironment':
https://github.com/processhacker/processhacker/blob/ 04f18ea9a98374fb5aa4fc0d8c51b93a708eafc4/phlib/native.c#L913
ProcessHacker 2.x works as intended with Wine, showing remote process' command line and environment using that approach (see previous code references).
https://github.com/processhacker/processhacker/releases/download/v2.39/ processhacker-2.39-setup.exe
Regards
Also I'm getting a 404 with all of those links except the stackoverflow one.
Sorry, i see now, i have to copy and paste it into the browser because link was trimmed.