[Fwd: [21.1] work around cygwin readlink bug]

[Christopher Faylor]

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 <unistd.h>

       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 <andyp@bea.com>
To: xemacs-patches@xemacs.org
CC: xemacs-nt@xemacs.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