[ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-58

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

Hi folks,


I just uploaded a new Cygwin 1.7 test release, 1.7.0-58.

I still refrain from telling stuff like "this is the last test release",
but I still hope we're getting really close now, even after I had
screwed up so nicely with the 1.7.0-53 and 1.7.0-54 releases :-P

You know the drill by now, see the older test release announcements
as http://cygwin.com/ml/cygwin-announce/2009-07/msg00012.html


What's new in contrast to 1.7.0-57
===================================

- Nothing.


Bugfixes:
=========

- Fix and workaround a bug in the implementation of the C++ memory
  allocation support introduced in 1.7.0-49.  A structure pointer got
  accidentally manipulated when DLLs got loaded at runtime via dlopen.
  When dlclose'ing the same DLL, the pointer content pointed into the
  memory of the just unloaded DLL, with probably unexpected results.
  This fixes the problem reported in
  http://cygwin.com/ml/cygwin/2009-08/msg00352.html

- If the incoming length value in calls to accept(2), getsockname(2),
  and getpeername(2) is too small, the WinSock functions fail and simply
  return EFAULT.  POSIX demands that the functions don't fail, rather
  the returned socket address is just truncated to the given length.
  The length parameter itself returns with the full size of the
  underlying socket address.  Workaround the WinSock shortcoming so that
  the Cygwin functions accept(2), getsockname(2), and getpeername(2)
  behave POSIX-like.
  This fixes the problem reported in
  http://cygwin.com/ml/cygwin/2009-08/msg00372.html

- Return correct socket addresses for AF_UNIX/AF_LOCAL connections in
  calls to getsockname(2) and getpeername(2).  Return correct socket
  addresses for AF_UNIX/AF_LOCAL connections in calls to accept(2), most
  of the time.  We're currently not able to determine the correct peer
  address in accept(2) if the connecting AF_UNIX/AF_LOCAL socket has
  been bound.  So we just return the correct socket address content for
  an unbound peer, which covers 99.9% of the cases anyway.
  This fixes the problem observed in
  http://cygwin.com/ml/cygwin/2009-08/msg00386.html


FAQ:
====

- Q: How do I know that I'm running Cygwin 1.7.0-58?

  A: The `uname -v' command prints "2009-08-13 17:52"


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=3D3Dyourdomain.com@cygwin.com

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

http://cygwin.com/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 Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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