This is the mail archive of the
mailing list for the Cygwin project.
TEST RELEASE: Cygwin 2.2.0-0.2
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-announce at cygwin dot com
- Date: Wed, 22 Jul 2015 17:14:40 +0200
- Subject: TEST RELEASE: Cygwin 2.2.0-0.2
- Authentication-results: sourceware.org; auth=none
- Reply-to: The Cygwin Mailing List <cygwin at cygwin dot com>
Hi Cygwin friends and users,
I released a new TEST version of Cygwin. The version number is 2.2.0-0.2.
This test release needs some more good old-fashioned testing.
While the new features in this release are only interesting to
developers again, there's an intrusive under-the-hood change which just
needs testing in as many scenarios as possible.
==================================== tl;dr ==================================
Details aside, the interesting thing here is plain and simple this:
Does your stuff still work as with 2.1.0? No regression?
The boring details:
The under-the-hood change is this: Certain functions in Cygwin were
using very big buffers (32K, 64K, and more) on the stack. While this
is not much of a problem with the normal stacksize of 2 Megs, it's
been a lot of stack pressure on an application-provided patch. Yada,
For devs only:
NEW: sigsetjmp and siglongjmp were only implemented as macros so far.
POSIX requires functions longjmp and siglongjmp to exist. 2.2.0-0.2
adds sigsetjmp and siglongjmp functions.
2.2.0 comes with four new functions: getcontext, setcontext,
makecontext and swapcontext.
My own testing included two very simple self-written STCs, as well
as the example code from http://linux.die.net/man/3/makecontext, as
well as the glibc testcase tst-makecontext3.c.
As with the sigaltstack stuff, I'd be grateful if curious developers
would give this implementation a test. If it doesn't work as desired,
please consider to create simple reproduces in plain C.
Discussing aspects of this implementation may be best handled on the
cygwin-developers mailing list or the #cygwin-developers IRC channel
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com