From: Andrey Repin <anrdaemon@yandex.ru>
To: Corinna Vinschen <cygwin@cygwin.com>, cygwin@cygwin.com
Subject: Re: Privilege(s) needed to run top command
Date: Tue, 12 Mar 2019 21:50:00 -0000 [thread overview]
Message-ID: <1713374829.20190313003955@yandex.ru> (raw)
In-Reply-To: <20190312205929.GQ3785@calimero.vinschen.de>
Greetings, Corinna Vinschen!
> On Mar 12 23:35, Andrey Repin wrote:
>> 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.
> Same problem:
> https://docs.microsoft.com/en-us/windows/desktop/psapi/enumerating-all-processes
My bad. I checked the code on hand, but missed that last OpenProcess call.
My code working with visible windows and, indeed, is unable to catch
elevated window's path.
--
With best regards,
Andrey Repin
Wednesday, March 13, 2019 0:37:12
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-03-12 21:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 16:56 jwang
2019-03-11 20:29 ` L A Walsh
2019-03-11 20:41 ` Achim Gratz
2019-03-11 21:28 ` Corinna Vinschen
2019-03-11 21:40 ` Achim Gratz
2019-03-12 0:20 ` Andrey Repin
2019-03-12 8:58 ` Corinna Vinschen
2019-03-12 9:48 ` jwang
2019-03-12 11:14 ` Corinna Vinschen
2019-03-12 12:01 ` jwang
2019-03-12 12:39 ` Houder
2019-03-12 15:51 ` jwang
2019-03-12 16:47 ` Corinna Vinschen
2019-03-12 17:06 ` jwang
2019-03-12 17:13 ` Corinna Vinschen
2019-03-12 17:19 ` jwang
2019-03-12 17:40 ` Corinna Vinschen
2019-03-12 17:39 ` Corinna Vinschen
2019-03-12 20:28 ` Corinna Vinschen
2019-03-12 20:50 ` Andrey Repin
2019-03-12 20:59 ` Corinna Vinschen
2019-03-12 21:50 ` Andrey Repin [this message]
2019-03-12 18:10 ` Houder
2019-03-12 19:27 ` Achim Gratz
2019-03-13 9:17 ` jwang
2019-03-15 10:20 ` jwang
2019-03-15 11:28 ` Corinna Vinschen
2019-03-15 12:34 ` jwang
2019-03-15 13:38 ` Corinna Vinschen
2019-03-15 13:50 ` jwang
2019-03-15 14:11 ` jwang
2019-03-15 14:53 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1713374829.20190313003955@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).