DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:date:from:to:subject:message-id
	:mime-version:content-type; q=dns; s=default; b=ckmMLdbzyFUg9qq/
	IGtZTrsL/1SmIqOWg8tjd1dz5BG1uI6JfIA8a8JNqXL+CZoisfNMdkHpRqGr97Mx
	kHFIfoEkFKfZB88LXDFYZEjDBbS2Yck8X2ypMTp3Ppzi0OtnWU5UxZK7Kvsn7SBa
	Ja8sDSxR0cHWoGFYpT9IJ0FGBKw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Reply-To: cygwin AT cygwin DOT com
Date: Sat, 20 Jun 2015 22:55:12 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.1.0-0.1
Message-Id: <announce.20150620205512.GA28301@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)

Hi Cygwin friends and users,


I released a TEST version of Cygwin.  The version number is 2.1.0-0.1.

This test release is mostly for interested *developers*.

The important news which needs some testing is the implementation of
sigaltstack(2) and the underlying implementation of running a signal
handler on the alternate signal stack.

Implementation details:

- The alternate signal stack installed via sigaltstack is only valid
  for the current thread.  Each thread must call its own sigaltstack.
  On pthread_create, the alternate signal stack setting of the calling
  thread is *not* propagated to the newly created thread.  This follows
  current Linux semantics.

- The alternate signal stack is a minimal stack.  Certain datastructures
  used by Cygwin (_cygtls area) and Windows (on 32 bit: exception records)
  are not copied over to the alternate signal stack.  The stack settings
  in the Thread Environment Block (TEB) are not reflecting the current
  alternate stack while running the signal handler.  The TEB will still
  point to the original thread stack.  This seems to work nicely in my
  testing, but there may be Windows functions which stop working in this
  scenario.

- The 32 bit version stores the original stack register content at the
  base of the alternate stack.  If you screw this up while running
  the signal handler, your thread is doomed on return to the caller.

- The 64 bit version stores the information in callee-saved registers
  r12 and r13 per MS-ABI.

I'd be grateful if curious developers would give this new sigaltstack
implementation a whirl and report back if it's working for them as
desired/expected.  And if not, simple reproducers in plain C are most
welcome in this case.  Discussing aspects of this implementation may be
best handled on the cygwin-developers mailing list or the
#cygwin-developers IRC channel on Freenode.


All changes in this release so far:
===================================

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

- First cut of an implementation to allow signal handlers running on an
  alternate signal stack.
  
- New API sigaltstack, plus definitions for SA_ONSTACK, SS_ONSTACK, SS_DISABLE,
  MINSIGSTKSZ, SIGSTKSZ.

- New API: sethostname.


Bug Fixes
---------

- Enable non-SA_RESTART behaviour on threads other than main thread.
  Addresses: https://cygwin.com/ml/cygwin/2015-06/msg00260.html

- Try to handle concurrent close on socket more gracefully
  Addresses: https://cygwin.com/ml/cygwin/2015-06/msg00235.html


To install 32-bit Cygwin use https://cygwin.com/setup-x86.exe
To install 64 bit Cygwin use https://cygwin.com/setup-x86_64.exe


Have fun,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

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