[ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.2

[ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.2

[Corinna Vinschen]

Hi folks,


I uploaded a new Cygwin test release 3.1.0-0.2

This release comes with a couple of new features and quite a few
bug fixes.

The most interesting change, courtesy Ken Brown, is a revamp of the
old FIFO code.  It should now be possible to open FIFOs multiple times
for writing, something the old code failed on.


Please test.

=======================================================================

What's new:
-----------

- Add 24 bit color support using xterm compatibility mode in Windows 10
  1703 or later.  Add fake 24 bit color support for legacy console,
  which uses the nearest color from 16 system colors.

- New APIs: sched_getaffinity, sched_setaffinity, pthread_getaffinity_np,
  pthread_setaffinity_np, plus CPU_SET macros.

- New APIs: dbm_clearerr, dbm_close, dbm_delete, dbm_dirfno, dbm_error,
  dbm_fetch, dbm_firstkey, dbm_nextkey, dbm_open, dbm_store.


What changed:
-------------

- FIFOs can now be opened multiple times for writing.
  Addresses: https://cygwin.com/ml/cygwin/2015-03/msg00047.html
             https://cygwin.com/ml/cygwin/2015-12/msg00311.html

- If a SA_SIGINFO signal handler changes the ucontext_t pointed to by
  the third parameter, follow it after returning from the handler.

- Eliminate a header file name collision with <X11/XLocale.h> on case
  insensitive filesystems by reverting <xlocale.h> back to <sys/_locale.h>.


Bug Fixes
---------

- Fix select() on console in canonical mode.  Return after one line is
  completed, instead of when only one key is typed.

- Make console I/O functions thread-safe.

- Define missing MSG_EOR.  It's unsupported by the underlying Winsock
  layer so using it in send(2), sendto(2), or sendmsg(2) will return -1
  with errno set to EOPNOTSUPP and recvmsg(2) will never return it.

- Fix a timerfd deadlock.
  Addresses: https://cygwin.com/ml/cygwin/2019-06/msg00096.html

- Fix sigpending() incorrectly returning signals for unrelated threads.
  Addresses: https://cygwin.com/ml/cygwin/2019-07/msg00051.html

- Fix a hang when opening a FIFO with O_PATH.
  Addresses: https://cygwin.com/ml/cygwin-developers/2019-06/msg00001.html

- Don't append ".lnk" when renaming a socket file.
  Addresses: https://cygwin.com/ml/cygwin/2019-07/msg00139.html

- Make tcsetpgrp() return -1 if its argument is negative.
  Addresses: https://cygwin.com/ml/cygwin/2019-07/msg00166.html

- Avoid mistakenly moving a process under debugger control into the
  process group of the debugger.
  Addresses a problem visible in GDB 8.1.1, related to
  https://cygwin.com/ml/cygwin/2019-07/msg00166.html

- Return ENOEXEC from execve for arbitrary files only if the files are
  executable.
  Addresses: https://cygwin.com/ml/cygwin/2019-08/msg00054.html

- Fix off-by-one in environment evaluation leading to an abort.
  Addresses: https://cygwin.com/ml/cygwin-patches/2019-q3/msg00069.html

- Make output of /proc/[PID]/stat consistent with getpriority().
  Addresses: https://cygwin.com/ml/cygwin/2019-08/msg00082.html

- 64 bit only: Avoid collisions between memory maps created with shmat
  and Windows datastructures during fork.
  Addresses: https://cygwin.com/ml/cygwin/2019-08/msg00107.html
=======================================================================


Have fun,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

--
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

Re: [ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.2

[Takashi Yano]

Hi Corinna,

On Mon, 19 Aug 2019 12:39:56 +0200
Corinna Vinschen wrote:
> I uploaded a new Cygwin test release 3.1.0-0.2

I tested it in a short time and confirmed the bugs I reported recently
have been fixed.

One small thing I found is as follows.

Result of "ps | cat" in recent cygwin including this test release:
$ ps | cat
      PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND
     1930    1929    1930       7940  pty0      197609 21:32:53 /usr/bin/bash
     1942    1930    1941       6612  pty0      197609 21:33:14 /usr/bin/bash
     1941    1930    1941       1900  pty0      197609 21:33:14 /usr/bin/ps
     1929       1    1929       6644  ?         197609 21:32:53 /usr/bin/mintty

Expected result:
$ ps | cat
      PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND
     1930    1929    1930       7940  pty0      197609 21:32:53 /usr/bin/bash
     1942    1930    1941       6612  pty0      197609 21:33:14 /usr/bin/cat
     1941    1930    1941       1900  pty0      197609 21:33:14 /usr/bin/ps
     1929       1    1929       6644  ?         197609 21:32:53 /usr/bin/mintty

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
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

Re: [ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.2

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]

On Aug 19 21:49, Takashi Yano wrote:
> Hi Corinna,
> 
> On Mon, 19 Aug 2019 12:39:56 +0200
> Corinna Vinschen wrote:
> > I uploaded a new Cygwin test release 3.1.0-0.2
> 
> I tested it in a short time and confirmed the bugs I reported recently
> have been fixed.

Thanks for testing!

> One small thing I found is as follows.
> 
> Result of "ps | cat" in recent cygwin including this test release:
> $ ps | cat
>       PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND
>      1930    1929    1930       7940  pty0      197609 21:32:53 /usr/bin/bash
>      1942    1930    1941       6612  pty0      197609 21:33:14 /usr/bin/bash
>      1941    1930    1941       1900  pty0      197609 21:33:14 /usr/bin/ps
>      1929       1    1929       6644  ?         197609 21:32:53 /usr/bin/mintty
> 
> Expected result:
> $ ps | cat
>       PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND
>      1930    1929    1930       7940  pty0      197609 21:32:53 /usr/bin/bash
>      1942    1930    1941       6612  pty0      197609 21:33:14 /usr/bin/cat
>      1941    1930    1941       1900  pty0      197609 21:33:14 /usr/bin/ps
>      1929       1    1929       6644  ?         197609 21:32:53 /usr/bin/mintty

As far as I can tell this is not a bug.  I added debug output and found
that ps grabs the process list *before* bash execve's into cat.  So at
the time ps gets the process list, process 1942 in your example is
actually still bash.

If you call procps, which is slower than Cygwin's own ps, you tend
to see cat more often in this scenario.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.2

[Takashi Yano]

On Mon, 19 Aug 2019 16:00:40 +0200
Corinna Vinschen wrote:
> As far as I can tell this is not a bug.  I added debug output and found
> that ps grabs the process list *before* bash execve's into cat.  So at
> the time ps gets the process list, process 1942 in your example is
> actually still bash.
> 
> If you call procps, which is slower than Cygwin's own ps, you tend
> to see cat more often in this scenario.

Sounds reasonable. I wonder why this does not occur in linux...

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
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

Re: [ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.2

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

On Aug 20 00:03, Takashi Yano wrote:
> On Mon, 19 Aug 2019 16:00:40 +0200
> Corinna Vinschen wrote:
> > As far as I can tell this is not a bug.  I added debug output and found
> > that ps grabs the process list *before* bash execve's into cat.  So at
> > the time ps gets the process list, process 1942 in your example is
> > actually still bash.
> > 
> > If you call procps, which is slower than Cygwin's own ps, you tend
> > to see cat more often in this scenario.
> 
> Sounds reasonable. I wonder why this does not occur in linux...

It's way faster?  Consider that in Cygwin the "task switch" is
not performed by the OS, but basically by exec'ing and exec'd
process.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: TEST: Cygwin 3.1.0-0.2

[L A Walsh]

On 2019/08/19 03:39, Corinna Vinschen wrote:
> - Add 24 bit color support using xterm compatibility mode in Windows 10
>   1703 or later.  Add fake 24 bit color support for legacy console,
>   which uses the nearest color from 16 system colors.
>   
???  Why would xterm need Win10 for 24bit color?  I'm slightly confused --
is it only the non-X version that had this limitation?

tnx for the new stuff!
-linda



--
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

Re: TEST: Cygwin 3.1.0-0.2

[Takashi Yano]

On Wed, 21 Aug 2019 12:53:30 -0700
L A Walsh wrote:
> On 2019/08/19 03:39, Corinna Vinschen wrote:
> > - Add 24 bit color support using xterm compatibility mode in Windows 10
> >   1703 or later.  Add fake 24 bit color support for legacy console,
> >   which uses the nearest color from 16 system colors.
> >   
> ???  Why would xterm need Win10 for 24bit color?  I'm slightly confused --
> is it only the non-X version that had this limitation?

To tell the truth, git log says:
commit bd627864ab4189984cdb0892c00f91e39c4e8243
Cygwin: console: support 24 bit color

This feature is for console, that is, command prompt.
Command prompt in Win10 1703 has xterm compatible mode,
which is enabled by passing ENABLE_VIRTUAL_TERMINAL_PROCESSING
to SetConsoleMode().

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
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