Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 18 Dec 2000 19:54:54 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [Fwd: [21.1] work around cygwin readlink bug] Message-ID: <20001218195454.D4502@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3A3EA9F2 DOT E626B2B AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3A3EA9F2.E626B2B@ece.gatech.edu>; from cwilson@ece.gatech.edu on Mon, Dec 18, 2000 at 07:21:06PM -0500 On Mon, Dec 18, 2000 at 07:21:06PM -0500, Charles S. Wilson wrote: >Saw this message on the xemacs-nt mailing list. Is this a known bug in >cygwin-1.1.6 ? READLINK(2) Linux Programmer's Manual READLINK(2) NAME readlink - read value of a symbolic link SYNOPSIS #include int readlink(const char *path, char *buf, size_t bufsiz); DESCRIPTION readlink places the contents of the symbolic link path in the buffer buf, which has size bufsiz. readlink does not append a NUL character to buf. It will truncate the con- tents (to a length of bufsiz characters), in case the buffer is too small to hold all of the contents. I believe that the previous, incorrect behavior was discovered by Egor Duda's test suite. cgf -------- Original Message -------- Subject: [21.1] work around cygwin readlink bug Date: Mon, 18 Dec 2000 16:54:05 +0000 From: Andy Piper To: xemacs-patches AT xemacs DOT org CC: xemacs-nt AT xemacs DOT org Cygwin 1.1.6 seems to have introduced a bug in readlink which stop runemacs working correctly. This patch works around it by forcing a trailing 0 after .exe. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple