Date: Tue, 3 Apr 2012 16:37:01 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: [ANNOUNCEMENT] Updated: Cygwin 1.7.12
Message-Id: <announce.20120403143701.GA19014@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.21 (2010-09-15)
Reply-To: cygwin AT cygwin DOT com
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

Hi Cygwin friends and users,


I just released 1.7.12.  This is mainly a bugfix release, but a couple
of bigger changes were required under the hood to fix some of the bugs.


What's new:
===========

- Cygwin now automatically populates the /dev directory with all
  existing POSIX devices.

- Add virtual /proc/PID/mountinfo file.

- flock now additionally supports the following scenario, which requires
  to propagate locks to the parent process:

    (
      flock -n 9 || exit 1
      # ... commands executed under lock ...
    } 9>/var/lock/mylockfile

  Only propagation to the direct parent process is supported so far,
  not to grand parents or sibling processes.

- Add a "detect_bloda" setting for the CYGWIN environment variable to help
  finding potential BLODAs.


Bug fixes:
==========

- Fix a subtle, long-standing bug when reading the CYGWIN environment
  variable, which could result in overwriting unrelated memory.

- Fix wrong MB_CUR_MAX setting at process startup.

- Define tcgetsid with correct return type.

- Fix Ctrl-C handling in the console for Cygwin processes.
 
- Fix a bug in controlling tty handling when duplicating a console
  descriptor.

- More fixes to handle DLL loading correctly.

- Fix a problem with a Windows network function misbehaving if the
  stack of the current thread is in the high address area.  Typically
  this only affected 64 bit systems.

- Fix a bug in Cygwin executable recognition which could result in
  some applications not started correctly.

- Don't handle 0 bytes reads on pipes as EOF.

- Fix scenarios in which the signal handling between parent and child
  process were broken due to a race condition.

- Fix a memory leak in synchronization calls like sleep or
  pthread_cond_timedwait.

- Fix definitions of MCAST_INCLUDE and MCAST_EXCLUDE in cygwin/socket.h.

- Simplify system time handling, fix return values of clock_getres and
  clock_setres for CLOCK_REALTIME, and fix potential infinite loop due
  to overaggressive optimization.

- Avoid using a potentially unrelated handle as stdio handle.

- Fix a few potential crashes.


Have fun,
Corinna


    *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain DOT com AT cygwin DOT com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          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