This is the mail archive of the
mailing list for the Cygwin project.
Re: [Fwd: [21.1] work around cygwin readlink bug]
- To: cygwin at cygwin dot com
- Subject: Re: [Fwd: [21.1] work around cygwin readlink bug]
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Mon, 18 Dec 2000 19:54:54 -0500
- References: <3A3EA9F2.E626B2B@ece.gatech.edu>
- Reply-To: cygwin at cygwin dot com
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
READLINK(2) Linux Programmer's Manual READLINK(2)
readlink - read value of a symbolic link
int readlink(const char *path, char *buf, size_t bufsiz);
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.
-------- Original Message --------
Subject: [21.1] work around cygwin readlink bug
Date: Mon, 18 Dec 2000 16:54:05 +0000
From: Andy Piper <firstname.lastname@example.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