Re: GetVersionEx() depreciated, what should be used instead for Windows 7/8/10?
On Mar 23 10:57, Christian Franke via Cygwin wrote: > On Mar 21 16:15, Corinna Vinschen via Cygwin wrote: > > On Mar 21 09:58, Christian Franke via Cygwin wrote: > > > > > .. > > I just gave it a try on W11. The results are even more funny than I > > anticipated: > > > > ... > > > > So, yeah, with your observations especially on older W10 versions and > > with 8.1 doing the same thing, I guess we can safely drop the extra call > > to RtlGetNtVersionNumbers now. > > Or: > Keep RtlGetVersionNumbers, compare result with RtlGetVersion and emit debug > output if both differ. This would allow to diagnose a possible future > reappearance of the issue. Good idea! Do you want to create a patch? Thanks, Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Help with use of pgrep or pkill commands with full name options
J M via Cygwin writes: > Help with use of pgrep or pkill commands with full name options. > > I trying to use pgrep or pkill utility commands to find processes but using > the full path names, by example, find /usr/bin/bash (package procps-ng): > > Then, if I use pgrep -f /usr/bin/bash, don't find nothing. I note that on Cygwin: pgrep -f /bin/bash finds some but not all of my running bash processes. pgrep -a bash finds all of them. I leave it to others to explain why /usr/bin/bash doesn't work. I note that on (Debian) Linux the results of the above alternatives _also_ differ, but that pgrep -f /usr/bin/bash and pgrep -f /bin/bash both work and give the same results. ht -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND e-mail: h...@inf.ed.ac.uk URL: https://www.ltg.ed.ac.uk/~ht/ [mail from me _always_ has a .sig like this -- mail without it is forged spam] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: GetVersionEx() depreciated, what should be used instead for Windows 7/8/10?
On Mar 21 16:15, Corinna Vinschen via Cygwin wrote: On Mar 21 09:58, Christian Franke via Cygwin wrote: .. I just gave it a try on W11. The results are even more funny than I anticipated: ... So, yeah, with your observations especially on older W10 versions and with 8.1 doing the same thing, I guess we can safely drop the extra call to RtlGetNtVersionNumbers now. Or: Keep RtlGetVersionNumbers, compare result with RtlGetVersion and emit debug output if both differ. This would allow to diagnose a possible future reappearance of the issue. After such a long time, I don't know on which version of Windows we observed the problem. Some developer preview? Meantime I also tested with Win10 1607, 1703, 1709, 1803 VM snapshots with same result. -- Regards, Christian -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: GetVersionEx() depreciated, what should be used instead for Windows 7/8/10?
On Mar 22 18:13, Ray Satiro via Cygwin wrote: > On 3/21/2024 11:15 AM, Corinna Vinschen via Cygwin wrote: > >https://cygwin.com/cgit/newlib-cygwin/commit/?id=48511f3d3847c > > The code in that commit doesn't look right. RtlGetNtVersionNumbers is a void > function The code doesn't request a return value. > and the third parameter may not be just the build number. Fixed a month later: https://cygwin.com/cgit/newlib-cygwin/commit/?id=63f19278b998b Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
