From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] CALL FOR TESTING: Cygwin 1.7.12
Date: Fri, 30 Mar 2012 12:48:00 -0000 [thread overview]
Message-ID: <announce.20120330113350.GA12620@calimero.vinschen.de> (raw)
Hi folks,
we're about to release Cygwin 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.
Please test the latest developer snapshot from http://cygwin.com/snapshots/
That's what we think should become 1.7.12.
Please report bugs to the cygwin at cygwin dot com mailing list.
Please follow the guidelines at http://cygwin.com/problems.html
Be aware that we're mainly focusing on regressions from 1.7.11.
What's new:
===========
- Cygwin now automatically populates the /dev directory with all
existing POSIX devices.
- Add virtual /proc/PID/mountinfo file.
- flock now additionaly 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 subtil, 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 overagressive optimization.
- Avoid using a potentially unrelated handle as stdio handle.
- Fix a few potential crashes.
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.com@cygwin.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
next reply other threads:[~2012-03-30 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 12:48 Corinna Vinschen [this message]
2012-03-30 12:53 ` Eric Blake
2012-03-30 16:54 ` Nellis, Kenneth
2012-03-31 8:03 ` Denis Excoffier
2012-03-31 12:02 ` Thomas Wolff
2012-04-02 8:07 ` Corinna Vinschen
2012-04-02 17:06 ` Christopher Faylor
2012-04-02 18:51 ` Thomas Wolff
2012-04-02 18:54 ` Christopher Faylor
2012-04-01 20:06 Ken
2012-04-01 20:29 ` Christopher Faylor
2012-04-01 22:46 ` Christopher Faylor
2012-04-01 23:51 ` Ken
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=announce.20120330113350.GA12620@calimero.vinschen.de \
--to=corinna-cygwin@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).