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: [experimental] cygwin-1.5.25-11
Date: Wed, 05 Mar 2008 19:00:00 -0000	[thread overview]
Message-ID: <20080305185803.GC18446@calimero.vinschen.de> (raw)

I've uploaded another test version of the Cygwin DLL and its utilities,
version 1.5.25-11.

The main purpose of this update is to allow Cygwin to run correctly on
Windows 2008 Server.  A change in the exception handling in Windows 2008
Server requires to change the exception handling in the Cygwin DLL as
well, otherwise an exception in a Cygwin process results in an endless
loop in the OS, taking 100% CPU.  I reported this problem upstream.
The problem has been confirmed to be a missing check in one of the OS
DLLs.

Apart from that, this new release contains a couple of additional fixes
which cropped up in the last two months.

Please give it a test. 

The official release is now supposed to happen this weekend, finally.

Changes since version 1.5.25-10:

- Fix non-POSIX handling of ungetc buffer in ftell and fflush.

- Trying to create a directory with open("foo/") failes now with EISDIR.

- Fix a problem with CYGWIN=tty mode introduced in 1.5.25-8.

- Another change in exception handling.

Changes since version 1.5.25-9:

- Another change in exception handling.

Changes since version 1.5.25-8:

- Revert to the former Linux-like behaviour in exception handling.

Changes since version 1.5.25-7:

- Allow cygcheck to run on Windows 9x again.

- Fix testing for Samba shares to use more reliable test available with
  upcoming versions of Samba (3.0.28a, 3.2.0).

- Change exception handling to run under Windows 2008 Server.

- Fix a crash when creating stackdumps on Windows XP x64 Edition and
  Windows 2003 Server x64 Edition.

- Fix pthread_kill to deal with signal 0 as per POSIX.

- Fix ambiguity in thread signal mask handling.

- Try harder to make a pipe into a full-cygwin device.

- Fix strtod to handle incomplete hex strings correctly.


To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Save it and run setup, answer the questions, then look for
'cygwin' in the 'Base' category (it should already be selected).  You
will need to use the 'Exp' radio button to get the test version.

If you have questions or comments, please send them to the Cygwin
mailing list.  See http://cygwin.com/lists.html for details.

              *** 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
Red Hat

                 reply	other threads:[~2008-03-05 19:00 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=20080305185803.GC18446@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).