public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: TEST RELEASE: Cygwin 2.8.0-0.2
Date: Wed, 22 Mar 2017 20:14:00 -0000	[thread overview]
Message-ID: <20170322194849.GA11466@calimero.vinschen.de> (raw)

Hi folks,


I uploaded a new Cygwin test release 2.8.0-0.2

I'm planning for a release next week.  Yes, I already wrote that last
week.  I'm still trying to find the cause for a bug, but either way,
I'll release next week.  Please test.

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

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

- New API: timingsafe_bcmp, timingsafe_memcmp

- New API: dladdr


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

- cygcheck and strace now always generate output with Unix LF line endings,
  rather than with DOS/Windows CR LF line endings.

- fork now preserves the load order of unrelated dlopen'd modules.

- pthread_cond_wait now acts like Linux and BSD: Resume waiting for the
  condition variable as if it was not interrupted, rather than returning 0.


Bug Fixes
---------

- Fix a few problems which are the combined culprit of fork failing
  when called recursively from a pthread.
  Addresses: https://cygwin.com/ml/cygwin/2017-03/msg00113.html

- Fix potential buffer overflow in getrandom.

- Fix write(2) return value for writes > 2 GB.

- Workaround Windows NUL having the same problem for writes > 4 GB.
  Addresses: https://cygwin.com/ml/cygwin/2017-03/msg00144.html

- Fix a potential crash in duplocale.
  Addresses: https://sourceware.org/ml/newlib/2017/msg00166.html

- Fix dlopen/dlclose reference counting to make sure FreeLibrary isn't
  called too early in forked process.
  Addresses: https://cygwin.com/ml/cygwin/2017-03/msg00220.html

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


Thanks,
Corinna

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

                 reply	other threads:[~2017-03-22 20:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170322194849.GA11466@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-announce@cygwin.com \
    --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).