Greetings, Corinna Vinschen! > This was complete nonsense.
> Actually, the problem was entirely in Cygwin's ps.exe, and it's a > long-standing problem at that. > While the Cygwin DLL collected the complete process list for ps, ps then > didn't print any process it failed to call OpenProcess on. These are a > *lot* of processes and the result looked a lot like the list of > processes in or connected to the current session. > The reason for this behaviour was that the image path of a process could > only be fetched when opening the process. Today I found new > functionality since Vista which allows to fetch the image path without > having to open the process, so `ps -W' will print all processes again, > just as in the good old XP times :} Err, but why? PSAPI was available since… a long time since. And it is public API except for isolated processes. > Please try the latest snapshot from https://cygwin.com/snapshots/ > Make sure to use ps.exe from that snapshot since this time the ps > executable is affected, not the Cygwin DLL itself. -- With best regards, Andrey Repin Tuesday, March 12, 2019 23:34:43 Sorry for my terrible english...
