From: Bruno Haible <bruno@clisp.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: bug-gnulib@gnu.org
Subject: Re: ptsname_r on Cygwin
Date: Wed, 20 Jan 2021 09:11:25 +0100 [thread overview]
Message-ID: <3338673.hDtONKD4FM@omega> (raw)
In-Reply-To: <3482750.exAXJ2mfqj@omega>
> While https://www.kernel.org/doc/man-pages/online/pages/man3/ptsname_r.3.html
> says that ptsname_r, upon failure, should return an error code, on Cygwin,
> it returns 0 and stores the empty string in 'buffer'.
Let me document this issue.
2021-01-20 Bruno Haible <bruno@clisp.org>
doc: Document ptsname_r bug on Cygwin.
* doc/glibc-functions/ptsname_r.texi: Mention Cygwin bug.
diff --git a/doc/glibc-functions/ptsname_r.texi b/doc/glibc-functions/ptsname_r.texi
index 0bfd05b..a79e751 100644
--- a/doc/glibc-functions/ptsname_r.texi
+++ b/doc/glibc-functions/ptsname_r.texi
@@ -25,13 +25,17 @@ Mac OS X 10.5, FreeBSD 6.0, NetBSD 5.0, OpenBSD 6.7, Minix 3.1.8,
AIX 5.1, HP-UX 11, IRIX 6.5, Solaris 11.4, Cygwin 1.7.9, mingw,
MSVC 14.
@item
-When this functions fails, it returns -1 instead of the error code
+When this function fails, it returns -1 instead of the error code
on some platforms:
Mac OS X 10.13, Android 4.3.
@end itemize
Portability problems not fixed by Gnulib:
@itemize
+@item
+When this function fails, it returns 0 and stores an empty string as result
+on some platforms:
+Cygwin 2.9.
@end itemize
Note: Portable programs should expect to find the error code as the
next prev parent reply other threads:[~2021-01-20 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 6:31 ptsname_r on Cygwin Bruno Haible
2021-01-20 8:11 ` Bruno Haible [this message]
2021-01-21 18:21 ` Ken Brown
2021-01-21 20:26 ` Bruno Haible
2021-01-21 22:45 ` Ken Brown
2021-01-22 15:48 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3338673.hDtONKD4FM@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=kbrown@cornell.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).