This is the mail archive of the
mailing list for the Cygwin project.
Re: [1.7] Updated: cygwin-1.7.0-56
- From: Jim Reisert AD1C <jjreisert at alum dot mit dot edu>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Sun, 2 Aug 2009 09:45:56 -0600
- Subject: Re: [1.7] Updated: cygwin-1.7.0-56
- References: <20090730202942.GP18621@calimero.vinschen.de> <20090801201043.GA7072@ednor.casa.cgf.cx> <firstname.lastname@example.org>
It's worse than that.
In an xterm, the first "ls" works (I get output) but then nothing
works after that. Just get command prompt returned.
On Sun, Aug 2, 2009 at 9:41 AM, Jim Reisert AD1C<email@example.com> wrote:
> Emacs no longer works. ?It comes back to the prompt, no window.
> Using latest X-org and Emacs.
> - Jim
> On Sat, Aug 1, 2009 at 2:10 PM, Christopher
> Faylor<firstname.lastname@example.org> wrote:
>> I have uploaded a new Cygwin 1.7 test release, 1.7.0-56.
>> This fixes the bug introduced in -53 and -54 which resulted in various
>> problems execing programs as seen here:
>> What's new since 1.7.0-52
>> - Recognize non-NTFS remote filesystems which report to be NTFS as
>> ?"cifs" filesystems and avoid to call potentially unsupported NT call
>> ?in readdir().
>> - Made process startup slightly faster.
>> - Don't just return EBUSY when trying to remove shared files on an NFS
>> ?share. ?Rather, really try to remove them first.
>> - Fix a problem with text mode processing.
>> - Fix a typo in setlocale() which made the GBK charset disfunctional.
>> - Partially fix the FIFO regression reported in
>> - Fix a crash when trying to set long console title strings.
>> - Lower the memory usage of file descriptor data on the Cygwin heap.
>> ?This avoids to allocate 64K chunks per file. ?The new size is about
>> ?250 bytes + 4 * path length. ?This should fix the problem reported in
>> - Fix a problem in the destructor call order on process exit.
>> - Fix handling of incomplete UTF-8 sequences and rework UTF-16 surrogate
>> ?pair handling in mbrtowc() to be more bullet-proof. ?Check for invalid
>> ?Unicode valus beyond 0x10ffff.
>> - Q: How do I know that I'm running Cygwin 1.7.0-56?
>> ?A: cygcheck -c cygwin
Jim Reisert AD1C, <email@example.com>, http://www.ad1c.us
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple