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: Updated: Cygwin 1.7.31-2
Date: Mon, 21 Jul 2014 17:13:00 -0000	[thread overview]
Message-ID: <20140721171219.GR15332@calimero.vinschen.de> (raw)

Hi Cygwin friends and users,


I just released Cygwin 1.7.31-2.  This is mostely a bugfix release.

The only difference to 1.7.31-1 is the corrected initialization of
the main thread's thread mutex as outlined in
https://cygwin.com/ml/cygwin/2014-07/msg00248.html

Please note that the new passwd/group handling still isn't in this
version of Cygwin.  The changes are still work in progress.


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

- Improve performance of send(2), sendto(2), sendmsg(2) when using small
  input buffers.
  Addresses: https://cygwin.com/ml/cygwin/2014-07/msg00069.html

- The default pthread_mutex type is now PTHREAD_MUTEX_NORMAL, rather than
  PTHREAD_MUTEX_ERRORCHECK, just as on Linux.

- Align pthread_attr stack functions more closely to Linux.

- Mark pthread_attr_getstackaddr and pthread_attr_setstackaddr as deprecated,
  as on Linux.


Bug Fixes
---------

- Fix various assorted bugs (potential buffer overruns, resource leaks, you
  name it) caught by Coverity.

- Fix return value of getgrouplist if the number of groups is bigger than the
  application-provided buffer can hold.
  See https://cygwin.com/ml/cygwin/2014-05/msg00469.html

- Fix a spurious error condition in calls to getaddrinfo on x86_64.
  Addresses: https://cygwin.com/ml/cygwin/2014-06/msg00350.html

- Workaround a problem following native NTFS symlinks.  This patch has been
  not applied to 1.7.30, accidentally.
  Addresses: https://cygwin.com/ml/cygwin/2014-04/msg00384.html

- Fix an off-by-one bug in res_querydomain.
  Addresses: https://cygwin.com/ml/cygwin/2014-07/msg00052.html

- Don't catch STATUS_STACK_OVERFLOW preliminary on 64 bit.
  Fixes: https://cygwin.com/ml/cygwin/2014-07/msg00046.html

- Make sure that signals are properly delivered when sending lots of signals
  in succession.
  Fixes: https://cygwin.com/ml/cygwin/2014-07/threads.html#00149


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

The 64 bit Cygwin distribution doesn't yet come with as many packages
as the 32 bit version, but more packages will be available over time.

If you're already running a 32 bit version of Cygwin on 64 bit Windows
machines, you can continue to do so.  If you're planning a new install
of Cygwin on a 64 bit Windows machine, consider to use the new 64 bit
Cygwin version, unless you need certain packages not yet available in
the 64 bit release.


Have fun,
Corinna

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

                 reply	other threads:[~2014-07-21 17:13 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=20140721171219.GR15332@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).